ChromeWeb browser · Google
CVE-2026-14384
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 · uneditedOut of bounds read in ANGLE in Google Chrome on Windows prior to 150.0.7871.46 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 confidenceOut of bounds read vulnerability in ANGLE (a graphics abstraction layer used by Chrome) on Windows allows a remote attacker to leak cross-origin data via a crafted HTML page. This is an information disclosure vulnerability where the browser reads memory outside expected boundaries, potentially exposing sensitive data from other origins.
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.46CVSS 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.
-
Check Chrome version on WindowsNavigate to chrome://settings/help or run 'Google Chrome' and go to Menu > Help > About Google Chrome to view the installed version numberAffected if Version number is less than 150.0.7871.46 and the operating system is Windows
-
Confirm operating system is WindowsCheck system information via 'winver' command or System Properties - this vulnerability specifically affects Windows implementations of ANGLEAffected if The system is running Windows (the vulnerability is Windows-specific)
-
Verify ANGLE/graphics backend is in useNavigate to chrome://gpu and look for ' ANGLE ' in the Graphics Feature Status section - ANGLE is used by default for WebGL content on WindowsAffected if ANGLE is listed as the WebGL backend (which is default on Windows, enabling the attack surface)
-
Check if WebGL is enabledNavigate to chrome://settings/content or chrome://gpu and verify WebGL status - ANGLE is the graphics backend that provides WebGL on WindowsAffected if WebGL is enabled (the vulnerability triggers through WebGL content rendered via ANGLE)
User is affected if Chrome version is below 150.0.7871.46 on Windows with ANGLE/WebGL enabled, as the out-of-bounds read in the ANGLE graphics layer can be triggered by crafted 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.46
Update Google Chrome to version 150.0.7871.46 or later on Windows systems to patch the vulnerability.
Chrome 150.0.7871.46 or later
- Open Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is earlier than 150.0.7871.46, Chrome will automatically check for and install updates
- Restart Chrome after the update completes
- Verify the version is now 150.0.7871.46 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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-14384 — 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-14384 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