CVE-2026-103922: Capacitor Android and iOS: remote content can be loaded at the app origin via the internal HTTP proxy path
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 /capacitorhttpinterceptor. 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Capacitor Android and iOSto a version that resolves this vulnerability.Fixed in 6.2.2 - Upgrade
Upgrade
Capacitor Android and iOSto a version that resolves this vulnerability.Fixed in 7.6.9 - Upgrade
Upgrade
Capacitor Android and iOSto a version that resolves this vulnerability.Fixed in 8.3.5 - Upgrade
Upgrade
Capacitor Android and iOSto a version that resolves this vulnerability.Fixed in 8.4.3 - Upgrade
Upgrade
Capacitor Android and iOSto a version that resolves this vulnerability.Fixed in 8.5.1
Event History
Frequently Asked Questions
Which applications are exposed?
Android and iOS applications using Capacitor releases from 6.0.0 up to the listed fixed releases are exposed. The issue affects the WebView navigation guard and remains present even when CapacitorHttp is disabled.
What does an attacker need to exploit this issue?
An attacker needs to cause a victim to activate an untrusted link that navigates a frame to the internal /_capacitor_http_interceptor_ path. No attacker privileges are required, but user interaction is required.
What can an attacker access after successful exploitation?
The proxy can return attacker-selected remote content as a document at the application's origin. Script in that content can access same-origin storage, cookies, and registered Capacitor plugin capabilities.
What should teams do to remediate the issue?
Upgrade to Capacitor 6.2.2, 7.6.9, 8.3.5, 8.4.3, or 8.5.1, as appropriate for the deployed release line. Disabling CapacitorHttp alone does not mitigate the vulnerability.