ChromeWeb browser · Google
CVE-2026-8525
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 on Mac prior to 148.0.7778.168 allowed a remote attacker to potentially perform a sandbox escape 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 confidenceHeap buffer overflow vulnerability in ANGLE (a graphics translation layer) in Google Chrome on Mac before version 148.0.7778.168. A remote attacker can exploit this via a crafted HTML page to potentially escape the sandbox and execute arbitrary code.
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
< 148.0.7778.168CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 installed Chrome version on MacOpen Chrome, click the three-dot menu in the top-right, select Help > About Google Chrome. Alternatively, run 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString' in Terminal.Affected if Version is lower than 148.0.7778.168
-
Confirm operating system is macOSRun 'sw_vers' in Terminal or check System Settings > About on the Mac.Affected if System is running macOS (this vulnerability affects only Chrome on Mac)
-
Verify ANGLE graphics layer is in useIn Chrome, navigate to chrome://gpu and look for ' ANGLE ' or ' WebGL ' in the Graphics Feature Status section. ANGLE is used to translate OpenGL ES calls.Affected if ANGLE or WebGL is enabled and in use (the vulnerability lies within ANGLE's graphics handling)
You are affected if Google Chrome on macOS is installed with a version lower than 148.0.7778.168 and ANGLE/WebGL graphics features are enabled.
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 · scoped148.0.7778.168
Update Google Chrome to version 148.0.7778.168 or later on all affected Mac systems. Organizations should verify browser versions across their fleet and push updates as needed.
Chrome 148.0.7778.168 or later (stable release)
- Open Google Chrome on Mac
- Click on Chrome menu in the menu bar
- Select 'About Google Chrome'
- The browser will check for updates and display the current version
- If a version lower than 148.0.7778.168 is shown, Chrome will automatically download and offer to install the update
- Restart Chrome to complete the update
- Verify the version is now 148.0.7778.168 or later by checking About Google Chrome again
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
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 locallyCheck whether your project pulls in CVE-2026-8525 — 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-8525 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