ChromeWeb browser · Google
CVE-2026-14397
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 · uneditedOut of bounds write in ANGLE in Google Chrome on Mac prior to 150.0.7871.46 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 · moderate confidenceAn out-of-bounds write vulnerability in ANGLE (a graphics translation layer) in Google Chrome on Mac versions prior to 150.0.7871.46 allows a remote attacker to execute arbitrary code and potentially escape the sandbox via a specially crafted HTML page.
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
< 150.0.7871.46CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Confirm the operating system is MacRun 'uname -s' or check System Settings > About to verify the OS is macOS. This vulnerability only affects Chrome on Mac, not other platforms.Affected if The OS is not macOS - the user is NOT affected by this specific CVE
-
Check if Google Chrome is installedRun 'ls /Applications/Google Chrome.app' or check for Chrome in the Applications folder.Affected if Google Chrome is not installed - the user is NOT affected
-
Determine the installed Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' in Terminal.Affected if Unable to determine the version - manual verification required
-
Compare installed version against vulnerable rangeThe affected version range is any Google Chrome version on Mac prior to 150.0.7871.46. Compare your installed version number to this threshold.Affected if The installed version is 150.0.7871.46 or higher on Mac - the user is NOT affected; if the version is lower than 150.0.7871.46 on Mac, the user IS affected
The user is affected if running Google Chrome on macOS with a version lower than 150.0.7871.46.
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 · scoped150.0.7871.46
Update Google Chrome to version 150.0.7871.46 or later on all affected Mac systems to remediate this vulnerability.
Chrome 150.0.7871.46 or later for Mac
- Open Google Chrome on the affected Mac system
- Click on the Chrome menu (three dots) in the top-right corner
- Select 'Help' and then 'About Google Chrome'
- The browser will automatically check for and install the latest version
- Wait for version 150.0.7871.46 or later to be installed
- Restart Chrome if prompted to complete the update
- Verify the installed version 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
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14397 — 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-14397 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