Critical-Severity Flaw in ionic-team capacitor Tracked as CVE-2026-103922
A newly published critical vulnerability in ionic-team capacitor carries a CVSS score of 9.3. Here is what is affected and how to respond.
Key points
- CVE-2026-103922 affects ionic-team capacitor.
- CVSS 9.3 (Critical).
- No exploitation confirmed yet.
A critical security flaw tracked as CVE-2026-103922 has been published in the National Vulnerability Database for ionic-team capacitor, with a CVSS base score of 9.3.
At a glance
- CVE
- CVE-2026-103922
- Product
- ionic-team capacitor
- CVSS
- 9.3 Critical
- Weakness
- CWE-346, CWE-441
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Ionic-Team | capacitor | >= 6.0.0, < 6.2.2, >= 7.0.0, < 7.6.9, >= 8.0.0, < 8.3.5, >= 8.3.5, < 8.4.3 |
| @Capacitor | android | >= 8.5.0, < 8.5.1, >= 8.3.5, < 8.4.3, >= 8.0.0, < 8.3.5, >= 7.0.0, < 7.6.9 |
| @Capacitor | ios | >= 8.5.0, < 8.5.1, >= 8.3.5, < 8.4.3, >= 8.0.0, < 8.3.5, >= 7.0.0, < 7.6.9 |
| Com.Capacitorjs | core | >= 8.5.0, < 8.5.1, >= 8.3.5, < 8.4.3, >= 8.0.0, < 8.3.5, >= 7.0.0, < 7.6.9 |
| Swift | github.com/ionic-team/capacitor-swift-pm | >= 8.5.0, < 8.5.1, >= 8.3.5, < 8.4.3, >= 8.0.0, < 8.3.5, >= 7.0.0, < 7.6.9 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-103922
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-103922?
CVE-2026-103922 is a CWE-346, CWE-441 vulnerability in ionic-team capacitor.
How severe is CVE-2026-103922?
It has a CVSS score of 9.3 Critical.
Is CVE-2026-103922 being exploited?
There is no public confirmation of exploitation at the time of publication.
