PatchSiren cyber security CVE debrief
CVE-2026-10010 Google CVE debrief
CVE-2026-10010 is a site isolation bypass vulnerability in Google Chrome on Android, published 2026-05-28. The flaw stems from inappropriate implementation in Input handling, allowing a remote attacker who has already compromised the renderer process to bypass site isolation protections via a crafted HTML page. Google has assigned this a High severity rating. The vulnerability affects Chrome on Android versions prior to 148.0.7778.216. Successful exploitation requires prior renderer compromise, indicating this is typically chained with other vulnerabilities rather than exploited standalone. Site isolation is a critical security boundary in Chrome that prevents malicious websites from accessing cross-origin data; bypassing it could enable theft of sensitive session data, cookies, or credentials from other origins. Organizations should prioritize updating Android Chrome installations to version 148.0.7778.216 or later. Given the High severity and the nature of site isolation bypasses, this vulnerability should be treated as significant for mobile enterprise environments and users accessing sensitive web applications.
- Vendor
- Product
- Chrome
- CVSS
- MEDIUM 5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-28
- Original CVE updated
- 2026-07-21
- Advisory published
- 2026-05-28
- Advisory updated
- 2026-07-21
Who should care
Organizations with Android device fleets, mobile security teams, enterprises with BYOD policies, users accessing sensitive web applications on Android Chrome
Technical summary
Inappropriate implementation in Input handling in Google Chrome on Android prior to 148.0.7778.216 allows site isolation bypass. Attack vector requires prior renderer process compromise via crafted HTML page. High severity per Chromium security rating. Fix available in stable channel update.
Defensive priority
high
Recommended defensive actions
- Update Google Chrome on Android devices to version 148.0.7778.216 or later
- Verify Chrome version across managed Android device fleets
- Review mobile browser security policies to enforce automatic updates
- Monitor for anomalous cross-origin data access attempts in web application logs
- Consider additional network segmentation for high-risk mobile browsing scenarios
Evidence notes
Vulnerability description confirms inappropriate implementation in Input component. Chrome Release blog reference indicates fix in stable channel update. Chromium issue tracker reference provides additional technical context. CVE published and modified dates both 2026-05-28T23:16:42.840Z per official record.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-10010 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-10010
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-10010 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-10010
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html
-
Source reference
Unverified legacy reference
URL: https://issues.chromium.org/issues/513995565
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.