@capacitor/android
Affected
- introduced
6.0.0, fixed6.2.2(semver)
Fixed versions
6.2.2
Fix
- Fixed version
6.2.2npm install @capacitor/[email protected]
Advisory
Also known as: CVE-2026-103922
Capacitor Android and iOS: remote content can be loaded at the app origin via the internal HTTP proxy path
Impact
Capacitor's WebView navigation guard validated only the host and scheme of a
target URL, not its path. Because the internal HTTP proxy path
(/_capacitor_http_interceptor_) is served at the application's own origin, a
frame navigation to it was always treated as in-app navigation and allowed.
Loading that path as a document caused the native layer to fetch an arbitrary,
caller-specified URL and return the response body to the WebView **at the app's
own origin**. Script in that response then ran with full same-origin trust:
access to localStorage, cookies, and every native capability the application
exposes through its registered Capacitor plugins.
The proxy handler was additionally served **regardless of whether theCapacitorHttp plugin was enabled**, so applications that never enabledCapacitorHttp were also affected.
Exploitation requires a victim to activate a link inside the application's
WebView. Any Capacitor application that renders user-controlled or unsanitized
links (chat messages, comments, rich-text content) is a viable delivery surface.
Both Android and iOS are affected.
Patches
Two changes on each platform:
CapacitorHttp is enabled, and never for a document (main frame) request.Legitimate CapacitorHttp usage is unaffected. fetch and XMLHttpRequest are
subresource requests and do not pass through the navigation guard.
Upgrade to a patched version, then rebuild and redistribute your application.
Workarounds
If you cannot upgrade immediately, note first that **disabling CapacitorHttp
is not sufficient** on affected versions, because the proxy path is served
regardless of that setting.
Registered plugins are consulted before the navigation guard runs, so a small
plugin can block the path. On Android, override shouldOverrideLoad(Uri url) and
return true when url.getPath() starts with /_capacitor_http_interceptor_.
On iOS, implement shouldOverrideLoad(_:) and return true for the same path.
Returning true cancels the navigation; return null/nil for all other URLs
so normal navigation is unchanged.
Independently, sanitize user-controlled link targets before rendering them in the
WebView.
Critical Basis: The source's own band: CRITICAL
6.0.0, fixed 6.2.2 (semver)6.2.2
6.2.2npm install @capacitor/[email protected]7.0.0, fixed 7.6.9 (semver)7.6.9
7.6.9npm install @capacitor/[email protected]6.0.0, fixed 6.2.2 (semver)6.2.2
6.2.2npm install @capacitor/[email protected]7.0.0, fixed 7.6.9 (semver)7.6.9
7.6.9npm install @capacitor/[email protected]8.5.0, fixed 8.5.1 (semver)8.5.1
8.5.1npm install @capacitor/[email protected]8.5.0, fixed 8.5.1 (semver)8.5.1
8.5.1npm install @capacitor/[email protected]8.3.5, fixed 8.4.3 (semver)8.4.3
8.4.3npm install @capacitor/[email protected]8.3.5, fixed 8.4.3 (semver)8.4.3
8.4.3npm install @capacitor/[email protected]8.0.0, last affected 8.3.4 (semver)None listed
No fixed version is listed.
8.0.0, last affected 8.3.4 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0