dbcve.org
ChromeWeb browser · Google

CVE-2026-4464

HIGH · 8.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 146.0.7680.153 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Integer overflow in ANGLE in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit heap corruption 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 confidence

Integer overflow in the ANGLE graphics translation layer in Google Chrome prior to version 146.0.7680.153 allows a remote attacker to trigger heap corruption via a specially crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 146.0.7680.153 or later. Organizations should ensure automated patch management deploys browser updates promptly.

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:< 146.0.7680.153

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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
    Locate the Chrome executable. On Windows: check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS: check /Applications/Google Chrome.app. On Linux: check common paths like /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Google Chrome is not installed on the system
  2. Retrieve the installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command line (Linux), or right-click the Chrome shortcut and select Properties > Details (Windows), or run 'defaults read /Applications/Google\ Chrome.app/Contents/Info.plist CFBundleShortVersionString' (macOS).
    Affected if Unable to determine the installed version
  3. Compare version against the affected range
    Take the installed version number (e.g., 146.0.7680.125) and compare it numerically to 146.0.7680.153. The vulnerability affects all versions prior to 146.0.7680.153.
    Affected if Installed version is less than 146.0.7680.153 (for example, 146.0.7680.125, 145.0.6101.90, or any earlier version)
  4. Confirm the ANGLE graphics component is in use
    This is typically enabled by default for WebGL support. To check in Chrome, navigate to chrome://components and look for ANGLE. If WebGL is functional in the browser, ANGLE is active.
    Affected if WebGL is functional and ANGLE component is present (the vulnerability requires ANGLE to be active to be exploitable)

You are affected if Google Chrome is installed with a version lower than 146.0.7680.153 and the ANGLE graphics layer is in use (which is the default for WebGL functionality).

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 146.0.7680.153 or later
Fixed in 146.0.7680.153
Interim mitigation

Update Google Chrome to version 146.0.7680.153 or later. Organizations should ensure automated patch management deploys browser updates promptly.

Recommended fix High confidence

Chrome version 146.0.7680.153 or later

  1. 1. Open Google Chrome browser
  2. 2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
  3. 3. The browser will check for updates and display the current version
  4. 4. If a version older than 146.0.7680.153 is detected, click 'Update Google Chrome'
  5. 5. Wait for the update to download and install
  6. 6. Restart the browser to apply the update
  7. 7. Verify the version is now 146.0.7680.153 or later by returning to 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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4464 — 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-4464 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