ChromeWeb browser · Google
CVE-2026-14008
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 · uneditedUninitialized Use in WebXR in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory 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 confidenceUninitialized Use vulnerability in WebXR (Web Extended Reality) in Google Chrome on Android prior to version 150.0.7871.47 allows a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. This is an information disclosure vulnerability where memory is read before proper initialization.
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 the browser and platformVerify that Google Chrome is installed on an Android device. This vulnerability only affects Google Chrome on Android, not other browsers or platforms. Check by opening Chrome and confirming it is the Google browser on an Android phone or tablet.Affected if The device is running Google Chrome on Android.
-
Check the Chrome version on AndroidOpen Chrome on the Android device, tap the three-dot menu, go to Settings, then scroll down and tap 'About Chrome' or 'Chrome version' to view the current version number.Affected if The installed version is lower than 150.0.7871.47.
-
Confirm WebXR functionality is presentWebXR is built into Chrome for Android as a web standard feature. No separate enablement is required. The vulnerability exists in the WebXR implementation itself, so any use of WebXR-based websites could potentially trigger the flaw.Affected if WebXR features are accessible in the browser (WebXR is enabled by default in Chrome).
A user is affected if they are running Google Chrome on Android with a version lower than 150.0.7871.47 and use WebXR-capable websites.
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
Update Google Chrome for Android to version 150.0.7871.47 or later. Ensure browser auto-updates are enabled on affected devices.
Chrome for Android version 150.0.7871.47 or later
- Open the Google Play Store on the Android device
- Search for 'Google Chrome' in the app store
- Tap the 'Update' button to install the latest version of Chrome for Android
- Alternatively, ensure automatic updates are enabled in the Play Store settings to receive the patch automatically
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14008 — 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-14008 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