ChromeWeb browser · Google
CVE-2026-4448
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 · uneditedHeap buffer 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: High)
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 heap buffer overflow vulnerability exists in ANGLE (a graphics translation layer used by Chrome) that allows remote attackers to corrupt heap memory through specially crafted HTML pages. This memory corruption can potentially be leveraged for code execution or further exploitation.
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
< 146.0.7680.153CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome is installedOpen Chrome and navigate to chrome://version or check Programs and Features (Windows) / Applications folder (Mac)Affected if Google Chrome is present on the system
-
Retrieve installed Chrome versionType chrome://version in the address bar and locate the version number listed as 'Google Chrome X.X.X.X'Affected if Unable to determine version or Chrome is not installed
-
Compare against affected version rangeCompare the installed version number to 146.0.7680.153 - any version lower than this is affectedAffected if Installed version is less than 146.0.7680.153 (for example, 146.0.7680.125 or earlier)
-
Verify ANGLE is in useNavigate to chrome://gpu and look for 'ANGLE' or 'Graphics Feature Status' section showing WebGL is using ANGLEAffected if WebGL is enabled and using ANGLE as the backend (ANGLE is Chrome's default for WebGL on Windows)
-
Check if WebGL is accessible to webpagesVisit a WebGL test site (or chrome://gpu) - if WebGL is available, crafted HTML pages could trigger the vulnerabilityAffected if WebGL is listed as enabled in chrome://gpu
A user is affected if Google Chrome with a version lower than 146.0.7680.153 is installed and WebGL/ANGLE is accessible (the default state on most Chrome installations).
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 · scoped146.0.7680.153
Update Google Chrome to version 146.0.7680.153 or later to patch the vulnerability.
Chrome 146.0.7680.153
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- The browser will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- Restart the browser to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4448 — 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-4448 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