ChromeWeb browser · Google
CVE-2026-13923
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 GPU 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 confidenceThis is an uninitialized memory use vulnerability in the GPU rendering component of Google Chrome on Android. A remote attacker can exploit this by serving a specially crafted HTML page that triggers the uninitialized memory read, potentially exposing sensitive data from the browser process memory space.
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 version on AndroidOpen Settings > Apps > Google Chrome, or use ADB command: `adb shell dumpsys package com.android.chrome | grep versionName`Affected if Version displayed is below 150.0.7871.47
-
Confirm Chrome is the default browserCheck if Chrome handles web links: Go to Settings > Apps > Default apps > Browser app, or inspect device policy via MDM consoleAffected if Chrome is set as the default browser and handles web URLs
-
Verify GPU rendering is activeChrome uses GPU rendering by default for web content. To confirm, navigate to chrome://gpu in Chrome and check if 'GPU compositing' shows as enabledAffected if GPU rendering is enabled (this is the default state)
The environment is affected if Google Chrome for Android is installed with a version lower than 150.0.7871.47 and is used as the default browser, as the vulnerability triggers through the GPU rendering component when processing 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
Update Google Chrome for Android to version 150.0.7871.47 or later. Organizations should ensure mobile device management (MDM) policies enforce automatic Chrome updates on managed Android devices.
Chrome 150.0.7871.47 or later for Android
- Open the Google Play Store app on your Android device
- Search for 'Google Chrome' or locate it in your installed applications
- If an update is available, tap the 'Update' button to install version 150.0.7871.47 or later
- Alternatively, enable automatic updates for Chrome in Play Store settings to ensure future security patches are applied
- After updating, verify the installed version by opening Chrome, tapping the three-dot menu, selecting 'Help', then 'About Google Chrome'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13923 — 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-13923 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