CVE-2026-103922 Capacitor Android and iOS: remote content can be loaded at the app origin via the internal HTTP proxy path
Attackers can load remote content at the app origin via an internal proxy, enabling access to same-origin storage and plugin capabilities.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-103922?
CVE-2026-103922 is a critical server-side request forgery vulnerability in @capacitor android, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by CVE-2026-103922?
40 open source packages ship an affected version, including @capacitor/android, com.capacitorjs:core and github.com/ionic-team/capacitor-swift-pm.
| Package | Affected | Fixed in |
|---|---|---|
@capacitor/android npm | From 6.0.0 | 6.2.2 |
@capacitor/android npm | From 6.0.0 | 6.2.2 |
@capacitor/android npm | From 7.0.0 | 7.6.9 |
@capacitor/android npm | From 7.0.0 | 7.6.9 |
@capacitor/android npm | From 8.0.0 to 8.3.4 | None |
@capacitor/android npm | From 8.0.0 to 8.3.4 | None |
34 more packages
@capacitor/android npm | From 8.3.5 | 8.4.3 |
@capacitor/android npm | From 8.3.5 | 8.4.3 |
@capacitor/android npm | From 8.5.0 | 8.5.1 |
@capacitor/android npm | From 8.5.0 | 8.5.1 |
com.capacitorjs:core Maven | From 6.0.0 | 6.2.2 |
com.capacitorjs:core Maven | From 6.0.0 | 6.2.2 |
com.capacitorjs:core Maven | From 7.0.0 | 7.6.9 |
com.capacitorjs:core Maven | From 7.0.0 | 7.6.9 |
com.capacitorjs:core Maven | From 8.0.0 to 8.3.4 | None |
com.capacitorjs:core Maven | From 8.0.0 to 8.3.4 | None |
com.capacitorjs:core Maven | From 8.3.5 | 8.4.3 |
com.capacitorjs:core Maven | From 8.3.5 | 8.4.3 |
com.capacitorjs:core Maven | From 8.5.0 | 8.5.1 |
com.capacitorjs:core Maven | From 8.5.0 | 8.5.1 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 6.0.0 | 6.2.2 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 6.0.0 | 6.2.2 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 7.0.0 | 7.6.9 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 7.0.0 | 7.6.9 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 8.0.0 to 8.3.4 | None |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 8.0.0 to 8.3.4 | None |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 8.3.5 | 8.4.3 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 8.3.5 | 8.4.3 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 8.5.0 | 8.5.1 |
github.com/ionic-team/capacitor-swift-pm SwiftURL | From 8.5.0 | 8.5.1 |
@capacitor/ios npm | From 6.0.0 | 6.2.2 |
@capacitor/ios npm | From 6.0.0 | 6.2.2 |
@capacitor/ios npm | From 7.0.0 | 7.6.9 |
@capacitor/ios npm | From 7.0.0 | 7.6.9 |
@capacitor/ios npm | From 8.0.0 to 8.3.4 | None |
@capacitor/ios npm | From 8.0.0 to 8.3.4 | None |
@capacitor/ios npm | From 8.3.5 | 8.4.3 |
@capacitor/ios npm | From 8.3.5 | 8.4.3 |
@capacitor/ios npm | From 8.5.0 | 8.5.1 |
@capacitor/ios npm | From 8.5.0 | 8.5.1 |
How do I fix CVE-2026-103922?
Upgrade @capacitor/android to a fixed version for your release line: 6.2.2, 7.6.9, 8.4.3 or 8.5.1.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-103922 being exploited?
There is no known exploitation of CVE-2026-103922 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-rvm3-566m-v7fv.