CVE-2026-103922: ionic-team capacitor · Origin Validation Error
Affects ionic-team capacitorSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical · fixed in 8.5.1 : patch ionic-team capacitor as a priority.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.5.1, 8.4.3, 8.3.5 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ionic-teamcapacitor | Affected
| Fixed in
|
| ionic-teamcapacitor | Affected
| Fixed in
|
| ionic-teamcapacitor | Affected
| Fixed in
|
| ionic-teamcapacitor | Affected
| Fixed in
|
| ionic-teamcapacitor | Affected
| Fixed in
|
| @capacitorandroid | Affected
| Fixed in
|
AI-suggested
A fix is available in Capacitor versions 6.2.2, 7.6.9, 8.3.5, 8.4.3, and 8.5.1. Users should upgrade to these versions to remediate the vulnerability. Since the issue persists even when CapacitorHttp is disabled, disabling this feature is not an effective mitigation. No other vendor advisory or temporary workaround is provided.
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.
References
- github.com/ionic-team/capacitor/security/advisories/GHSA-rvm3-566m-v7fv (opens in a new tab)
- github.com/ionic-team/capacitor/commit/430356a91e1419fc66862dc09835081aa501677e (opens in a new tab)
- github.com/ionic-team/capacitor/commit/80b6c5e81d062e1e158914040f49e044d95b7ccb (opens in a new tab)
- github.com/ionic-team/capacitor/commit/85ccc44151fdd5ae5e0d806d875766ef4b84ad5d (opens in a new tab)
- github.com/ionic-team/capacitor/commit/af9a287fef45f0ac68ce640cb42fed2d06b0f1b4 (opens in a new tab)
- github.com/ionic-team/capacitor/commit/d5e3170ba0ff155fc542b7e6d16cff5201406540 (opens in a new tab)
- github.com/ionic-team/capacitor/commit/ee586ae680887ba99d066616f976db149542d922 (opens in a new tab)
- github.com/ionic-team/capacitor/releases/tag/8.5.1 (opens in a new tab)