ChromeWeb browser · Google
CVE-2026-5879
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 · uneditedInsufficient validation of untrusted input in ANGLE in Google Chrome on Mac prior to 147.0.7727.55 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceA vulnerability in Google's ANGLE graphics abstraction layer in Chrome for Mac allows remote attackers to execute arbitrary code via a crafted HTML page due to insufficient validation of untrusted input. Although code execution occurs within a sandbox, the high CVSS score (8.8) indicates significant impact 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
< 147.0.7727.55CVSS 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 installed on MacOpen Terminal and run: ls /Applications/ | grep -i chromeAffected if Google Chrome.app exists in /Applications
-
Check installed Chrome version on MacOpen Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if Command returns a version number
-
Compare the version from --version against 147.0.7727.55 - any version lower than 147.0.7727.55 is affectedAffected if Installed version is less than 147.0.7727.55 (e.g., 147.0.7727.54, 146.x.x.x, etc.)
-
Verify this is Mac specificallyConfirm the operating system is macOS - run: uname -s in TerminalAffected if Operating system is macOS and Chrome version is below 147.0.7727.55
User is affected if Google Chrome is installed on macOS and the installed version is lower than 147.0.7727.55
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 · scoped147.0.7727.55
Update Google Chrome for Mac to version 147.0.7727.55 or later to remediate this input validation vulnerability.
Chrome version 147.0.7727.55
- Open Google Chrome on your Mac device
- Click on the Chrome menu (three dots) in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- Chrome will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- Wait for the download and installation to complete
- Restart Google Chrome 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
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-5879 — 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-5879 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