dbcve.org
ChromeWeb browser · Google

CVE-2026-5275

HIGH · 8.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 146.0.7680.177 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
Heap buffer overflow in ANGLE in Google Chrome on Mac prior to 146.0.7680.178 allowed a remote attacker to execute arbitrary code 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 confidence

Heap buffer overflow vulnerability in ANGLE graphics library component of Google Chrome on macOS allows remote attackers to execute arbitrary code via malicious HTML pages. The overflow occurs in heap memory allocation, potentially enabling memory corruption and code execution.

MitigationUpdate Google Chrome for Mac to version 146.0.7680.178 or later to patch the vulnerability. Organizations should ensure automated browser update mechanisms are enabled or distribute the update via enterprise patch management.

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.177

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 on macOS
    Check for the Chrome application bundle: ls -la "/Applications/Google Chrome.app" or search in Applications folder
    Affected if Google Chrome.app does not exist in /Applications - not affected if not installed
  2. Determine installed Google Chrome version on macOS
    Run: defaults read "/Applications/Google Chrome.app/Contents/Info.plist" CFBundleShortVersionString
    Affected if Cannot read version from Info.plist - Chrome may not be properly installed
  3. Compare installed version against affected range
    Compare the version obtained from Step 2 to the affected range: any version below 146.0.7680.177 is vulnerable. Version 146.0.7680.177 itself and above (starting with 146.0.7680.178) are patched
    Affected if Installed version is 146.0.7680.177 or lower - user is running a vulnerable version
  4. Confirm platform is macOS
    This vulnerability specifically affects macOS. Verify by running: uname -s (should return Darwin)
    Affected if Not running macOS - this specific CVE does not apply to other platforms
  5. Verify ANGLE graphics library is in use
    Open chrome://gpu in Chrome browser and look for 'ANGLE' in the Graphics Feature Status section, or check chrome://flags for ANGLE-related settings
    Affected if ANGLE is enabled - the vulnerable component is active; if ANGLE is disabled, exploitation may not be possible though version should still be checked

User is affected if running Google Chrome on macOS with version 146.0.7680.177 or lower and ANGLE graphics library is enabled (default state).

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.177 or later
Fixed in 146.0.7680.177
Interim mitigation

Update Google Chrome for Mac to version 146.0.7680.178 or later to patch the vulnerability. Organizations should ensure automated browser update mechanisms are enabled or distribute the update via enterprise patch management.

Recommended fix High confidence

Google Chrome 146.0.7680.178 or later

  1. 1. Open Google Chrome on the Mac system
  2. 2. Click on the three-dot menu in the top-right corner
  3. 3. Select 'Help' and then 'About Google Chrome'
  4. 4. Chrome will check for updates automatically
  5. 5. If an update is available, click 'Update Google Chrome'
  6. 6. 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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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