dbcve.org
ChromeWeb browser · Google

CVE-2026-14425

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 150.0.7871.46 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 8 weeks old

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 · unedited
Use 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 coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced 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 confidence

Use after free vulnerability in Google's ANGLE graphics library in Chrome prior to version 150.0.7871.46 allows a remote attacker to potentially escape the browser's sandbox via a specially crafted HTML page. The UAF occurs in the ANGLE component which translates OpenGL calls, enabling memory corruption that can bypass Chrome's sandbox isolation.

MitigationUpdate Google Chrome to version 150.0.7871.46 or later to patch the vulnerability. Organizations should prioritize this update given the CVSS 9.6 severity and sandbox escape potential.

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
Affected:< 150.0.7871.46

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Google Chrome is installed
    Check for Chrome installation: On Windows, look for Chrome in Program Files or via 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome"' or check for chrome.exe in common paths. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or via package manager.
    Affected if Chrome is not installed on the system
  2. Determine installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' on Linux, or check the version property via Windows Registry at 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome'
    Affected if Version is less than 150.0.7871.46 (e.g., 149.x, 148.x, etc.)
  3. Confirm ANGLE component usage context
    ANGLE (Almost Native Graphics Layer Engine) is used automatically by Chrome when rendering WebGL content. Check if WebGL is enabled: navigate to chrome://gpu in Chrome and look for 'WebGL' in the Graphics Feature Status section. ANGLE translates OpenGL ES calls to native graphics APIs.
    Affected if WebGL is enabled and in use; the vulnerability triggers when rendering specially crafted WebGL content via ANGLE

A user is affected if they are running Google Chrome version below 150.0.7871.46 and use WebGL content (common in many web games, 3D applications, and graphics-heavy websites), as the UAF flaw exists in the ANGLE graphics translation component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 150.0.7871.46 or later
Fixed in 150.0.7871.46
Interim mitigation

Update Google Chrome to version 150.0.7871.46 or later to patch the vulnerability. Organizations should prioritize this update given the CVSS 9.6 severity and sandbox escape potential.

Recommended fix High confidence

Chrome 150.0.7871.46 or later

  1. Open Google Chrome browser
  2. Navigate to Chrome menu > Help > About Google Chrome
  3. Google Chrome will automatically check for and download updates
  4. Install any available updates to reach version 150.0.7871.46 or later
  5. Restart the browser after the update completes
  6. Alternatively, download the latest stable Chrome version directly from https://www.google.com/chrome/ and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14425 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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