ChromeWeb browser · Google
CVE-2026-13943
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 CSS 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 confidenceAn uninitialized use vulnerability exists in Chrome's CSS parser on Android. By tricking a user into visiting a crafted HTML page, a remote attacker can trigger the browser to read uninitialized memory and expose potentially sensitive information from the process memory.
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.
-
Verify Chrome for Android is installedOpen device Settings > Apps > look for Google Chrome in the app list, or check chrome://version in the Chrome browserAffected if Chrome for Android is not installed then this CVE does not apply to that device
-
Determine the installed Chrome versionOpen Chrome on the Android device, navigate to chrome://version, and locate the version number shown at the top of the pageAffected if Unable to retrieve a version number means Chrome is either not present or inaccessible for inspection
-
Compare the version against the affected rangeTake the version number from chrome://version (e.g., 150.0.7871.47) and compare it numerically to 150.0.7871.47. Any version with a lower major, minor, or patch number is in the affected rangeAffected if Installed version is less than 150.0.7871.47 (e.g., 149.x.x.x or 150.0.7871.0) indicates the device is vulnerable
-
Confirm the attack surface is accessibleThe vulnerability is triggered by a user visiting a crafted HTML page. Determine if the browser is used to browse the web or render untrusted contentAffected if If Chrome is never used to visit web pages, the exploit requires user interaction and cannot be triggered passively
A defender is affected if Google Chrome for Android is installed with a version number lower than 150.0.7871.47 and the browser is used to visit 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.
Chrome Android 150.0.7871.47 or later
- Open Google Chrome on the Android device
- Tap the three-dot menu icon in the top-right corner
- Scroll down and tap Settings
- Tap Help & feedback, then tap About Chrome
- Chrome will automatically check for updates
- If version 150.0.7871.47 or later is available, tap Update to download and install it
- Restart Chrome to complete the update process
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.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-13943 — 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-13943 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