CVE Tools

CVE-2026-103922

Capacitor Android and iOS: remote content can be loaded at the app origin via the internal HTTP proxy path

No known exploitation. EPSS puts it in the 11th percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Ionic-team CapacitorAffected: >= 6.0.0, < 6.2.2Upgrade to: not statedAffected: >= 7.0.0, < 7.6.9Upgrade to: not statedAffected: >= 8.0.0, < 8.3.5Upgrade to: not statedAffected: >= 8.3.5, < 8.4.3Upgrade to: not stated + 1 more branchStated by: CVE record
  • @capacitor AndroidAffected: >= 8.5.0, < 8.5.1Upgrade to: not statedAffected: >= 8.3.5, < 8.4.3Upgrade to: not statedAffected: >= 8.0.0, < 8.3.5Upgrade to: not statedAffected: >= 7.0.0, < 7.6.9Upgrade to: not stated + 1 more branchStated by: CVE record
  • @capacitor IosAffected: >= 8.5.0, < 8.5.1Upgrade to: not statedAffected: >= 8.3.5, < 8.4.3Upgrade to: not statedAffected: >= 8.0.0, < 8.3.5Upgrade to: not statedAffected: >= 7.0.0, < 7.6.9Upgrade to: not stated + 1 more branchStated by: CVE record
  • Com.capacitorjs CoreAffected: >= 8.5.0, < 8.5.1Upgrade to: not statedAffected: >= 8.3.5, < 8.4.3Upgrade to: not statedAffected: >= 8.0.0, < 8.3.5Upgrade to: not statedAffected: >= 7.0.0, < 7.6.9Upgrade to: not stated + 1 more branchStated by: CVE record
  • Swift Github.com/ionic-team/capacitor-swift-pmAffected: >= 8.5.0, < 8.5.1Upgrade to: not statedAffected: >= 8.3.5, < 8.4.3Upgrade to: not statedAffected: >= 8.0.0, < 8.3.5Upgrade to: not statedAffected: >= 7.0.0, < 7.6.9Upgrade to: not stated + 1 more branchStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

Capacitor is a cross-platform native runtime for web applications. From 6.0.0 until 6.2.2, 7.6.9, 8.3.5, 8.4.3, and 8.5.1, the Android and iOS WebView navigation guard validates a target URL's host and scheme but not its path, allowing a victim who activates an untrusted link to navigate a frame to /_capacitor_http_interceptor_. The native proxy can fetch an attacker-selected URL and return the response as a document at the application's own origin, allowing script in that response to access same-origin storage, cookies, and registered Capacitor plugin capabilities. Applications remain affected when CapacitorHttp is disabled because affected releases serve the proxy path regardless of that setting. This issue is fixed in versions 6.2.2, 7.6.9, 8.3.5, 8.4.3, and 8.5.1.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS11th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 11th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 1 day, from the signal feeds we watch.

  1. Record updated
  2. Publishedweakness classified, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Scored 9.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Android, not every advisory.