ChromeWeb browser · Google
CVE-2026-13910
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient policy enforcement in WebXR in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInsufficient policy enforcement in WebXR (Web Extended Reality) API in Google Chrome on Android prior to version 150.0.7871.47 allows a remote attacker to leak cross-origin data via a crafted HTML page. This is a Same-Origin Policy bypass in the WebXR device API that fails to properly restrict cross-origin access to XR session data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 150.0.7871.47CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Chrome on Android devices in your environmentUse your mobile device management (MDM) or inventory system to list devices running Google Chrome on the Android operating system.Affected if Any Android device with Chrome installed is potentially affected if the version is below 150.0.7871.47.
-
Check installed Chrome version on AndroidOn each Android device, open Chrome, tap the three-dot menu, go to Settings > About Chrome to view the version number.Affected if The version shown is less than 150.0.7871.47.
-
Compare version to affected rangeVerify the version number against the affected range: any version prior to 150.0.7871.47 is vulnerable.Affected if The installed version starts with 149, 148, or any lower major version number.
-
Determine WebXR API usageReview any internal web applications or trusted sites that utilize WebXR (Web Extended Reality) functionality, as the vulnerability allows cross-origin data leakage when WebXR sessions are active.Affected if WebXR-enabled web applications are accessed on vulnerable Chrome versions.
A user is affected if they run Google Chrome on Android with a version lower than 150.0.7871.47 and use or access WebXR-enabled web content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped150.0.7871.47
Upgrade Google Chrome on Android to version 150.0.7871.47 or later. Organizations should ensure mobile devices receive Chrome updates through their MDM or patch management systems.
Chrome 150.0.7871.47 or later for Android
- Open the Google Play Store app on the Android device
- Search for 'Google Chrome' in the Play Store
- Tap the 'Update' button next to Google Chrome to install version 150.0.7871.47 or later
- Alternatively, open Chrome and navigate to chrome://settings/help to check for and apply updates
- After updating, restart Chrome to ensure the security patch is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13910 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data