ChromeWeb browser · Google
CVE-2026-14390
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 · uneditedUse after free in ANGLE in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceA use-after-free vulnerability in ANGLE (a graphics library used by Chrome for WebGL rendering) allows a remote attacker to exploit a freed memory object via a specially crafted HTML page. The vulnerability can potentially enable a sandbox escape, giving the attacker elevated privileges beyond Chrome's security sandbox.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 if Google Chrome is installedOpen terminal or command prompt and run: google-chrome --version (Linux), reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version (Windows), or /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version (macOS)Affected if Chrome is not installed - not affected
-
Verify Chrome version against affected rangeCompare the installed version number to 150.0.7871.46 - versions below this number are in the affected rangeAffected if Installed version is less than 150.0.7871.46
-
Confirm WebGL is enabled in ChromeOpen chrome://settings, search for 'Hardware acceleration' or 'WebGL', or visit chrome://gpu to check if WebGL/ANGLE rendering is available and enabledAffected if WebGL support is enabled (ANGLE library is loaded) - this is required for the vulnerability to be exploitable
-
Check Chrome update channelVisit chrome://settings/help or chrome://chrome to see if Chrome is receiving updates, or check if the browser is a frozen/third-party package that may not receive patchesAffected if Chrome is on a slow-update or enterprise-managed channel that may not have the patch deployed
User is affected if Google Chrome version is below 150.0.7871.46 AND WebGL/ANGLE rendering is enabled in the browser settings
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 to patch the vulnerability. Prior to deployment, test WebGL-dependent applications for compatibility in a staging environment.
Chrome 150.0.7871.46 or later
- Open Google Chrome
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates
- If an update is available, click 'Update Google Chrome'
- Restart the browser to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14390 — 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-14390 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