Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103922 Overview
CVE-2026-103922 is a critical origin validation flaw [CWE-346] in Ionic Capacitor, a cross-platform native runtime for web applications. The Android and iOS WebView navigation guard validates a target URL's host and scheme but ignores the path. An attacker can trick a victim into activating an untrusted link that navigates a frame to /_capacitor_http_interceptor_. The native proxy then fetches an attacker-selected URL and returns the response as a document at the application's own origin. Script in that response gains access to same-origin storage, cookies, and registered Capacitor plugin capabilities. The flaw affects releases from 6.0.0 through 6.2.1, 7.6.8, 8.3.4, 8.4.2, and 8.5.0.
Critical Impact
Attacker-controlled script executes at the application's origin with full Capacitor bridge access, even when CapacitorHttp is disabled.
Affected Products
- Ionic Capacitor Android and iOS runtime, versions 6.0.0 through 6.2.1
- Ionic Capacitor 7.x releases prior to 7.6.9
- Ionic Capacitor 8.x releases prior to 8.3.5, 8.4.3, and 8.5.1
Discovery Timeline
- 2026-10-01 - CVE-2026-103922 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-103922
Vulnerability Analysis
Capacitor exposes an internal HTTP proxy path, /_capacitor_http_interceptor_, intended to serve XHR and fetch subresources on behalf of the CapacitorHttp plugin. The WebView navigation guard in affected releases compares only the host and scheme of a candidate URL against the configured application origin. The URL path is not evaluated. An attacker who entices a user to activate a crafted link can navigate a frame directly to the proxy endpoint. The proxy then issues a request to an attacker-controlled URL and returns the fetched body as a document rendered at the application's origin.
Because the response renders at the app origin, the injected script inherits same-origin privileges. This includes read and write access to localStorage, IndexedDB, cookies, and any Capacitor plugin bridge available to the application. The exploit requires a single user interaction and does not require any special privilege on the target device.
Root Cause
The navigation guard in Bridge.java performed host and scheme equality checks against appUrl without inspecting the request path. The WebViewLocalServer handler served the proxy response for any request matching the interceptor path prefix, including main-frame navigations. Affected releases also served the proxy regardless of whether CapacitorHttp was enabled in the application configuration.
Attack Vector
Exploitation requires a victim to activate an untrusted link, such as a deep link, in-app link, or an iframe navigation. Once the frame navigates to the interceptor path with an attacker-chosen target URL, the proxied content is rendered at the app origin with full bridge access.
The upstream fix adds a path check in Bridge.java to block navigation to the interceptor path and gates the local server handler on both the CapacitorHttp enabled flag and the request type:
// Bridge.java - block frame navigation to the internal HTTP proxy path
String path = url.getPath();
if (path != null && path.startsWith(CAPACITOR_HTTP_INTERCEPTOR_START)) {
return true;
}
Uri appUri = Uri.parse(appUrl);
if (
!(appUri.getHost().equals(url.getHost()) && url.getScheme().equals(appUri.getScheme())) &&
// WebViewLocalServer.java - only serve the proxy for XHR/fetch subresources
if (null != loadingUrl.getPath() && loadingUrl.getPath().startsWith(Bridge.CAPACITOR_HTTP_INTERCEPTOR_START)) {
boolean httpEnabled = bridge.getConfig().getPluginConfiguration("CapacitorHttp").getBoolean("enabled", false);
if (!httpEnabled || request.isForMainFrame()) {
return null;
}
Logger.debug("Handling CapacitorHttp request: " + loadingUrl);
Source: GitHub Commit 430356a
Detection Methods for CVE-2026-103922
Indicators of Compromise
- WebView navigation events targeting any URL containing the path prefix /_capacitor_http_interceptor_
- Outbound HTTP requests from the mobile application to unexpected hosts originating from the native proxy handler
- Unexpected writes to application localStorage, IndexedDB, or cookie stores following a user-initiated link activation
Detection Strategies
- Perform static dependency scanning on mobile build artifacts to identify Capacitor runtime versions below 6.2.2, 7.6.9, 8.3.5, 8.4.3, or 8.5.1
- Instrument WebView navigation callbacks to log and alert on frame loads whose path begins with /_capacitor_http_interceptor_
- Review mobile telemetry for deep links or in-app navigations that resolve to the interceptor path with external url parameters
Monitoring Recommendations
- Enable server-side logging for application origins to correlate unexpected authenticated API traffic that may follow a successful bridge-origin compromise
- Monitor crash and analytics telemetry for anomalous script errors from app-origin pages shortly after link activation events
How to Mitigate CVE-2026-103922
Immediate Actions Required
- Upgrade Capacitor to a fixed release: 6.2.2, 7.6.9, 8.3.5, 8.4.3, or 8.5.1
- Rebuild and redistribute affected Android and iOS applications; disabling CapacitorHttp alone is not sufficient because affected releases serve the proxy path regardless of that setting
- Audit any custom shouldOverrideLoad plugin implementations to confirm they do not permit navigation to the interceptor path
Patch Information
The maintainers published fixes in the GitHub Security Advisory GHSA-rvm3-566m-v7fv and the GitHub Release 8.5.1. Core changes land in GitHub Commit 430356a and are backported in GitHub Commit 80b6c5e, GitHub Commit 85ccc44, GitHub Commit af9a287, GitHub Commit d5e3170, and GitHub Commit ee586ae.
Workarounds
- If immediate upgrade is not feasible, implement a custom WebViewClient or shouldOverrideLoad handler that rejects any navigation whose path starts with /_capacitor_http_interceptor_
- Restrict in-app link handling to a strict allow-list of trusted hosts and paths before passing URLs to the WebView
# Update Capacitor packages to a patched version
npm install @capacitor/core@8.5.1 @capacitor/android@8.5.1 @capacitor/ios@8.5.1
npx cap sync
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

