CVE-2026-14101 is a flaw (CVSS 9.6 in the record) in the Sandbox component of Google Chrome on Mac before 150.0.7871.47. Chromium rates its own severity Low. An attacker who compromised the renderer could escape the sandbox through a crafted page. Update Chrome to 150.0.7871.47 or later.
What's affected
The record says Google Chrome prior to 150.0.7871.47 is affected, on Mac only for this issue. The fixed version is 150.0.7871.47 or later. The record points to the June 2026 Chrome stable channel update post for the desktop release notes. That page loads its content with scripts and did not render for our fetch, so open it in a browser to see the exact build numbers per platform.
Other Chromium based browsers take Chromium fixes on their own schedule, so check each vendor.
How to check if you're exposed
Open chrome://version in the address bar and read the version number. Anything below 150.0.7871.47 is in range. To trigger an update, open the three dot menu, choose Help, then About Google Chrome, and relaunch when asked.
For managed fleets, check the version through your device management console or with a script that reads the installed Chrome version on each platform.
What to do now
- Open chrome://version and check the build is 150.0.7871.47 or later.
- Use About Google Chrome to update and relaunch the browser.
- Confirm your fleet policy lets Chrome update, and relaunch long running sessions.
- Check other Chromium based browsers and embedded runtimes such as Electron apps against their vendor advisories.
- Keep an eye on the Chrome releases blog for new stable updates.
Why it matters
The record lists improper privilege management and protection mechanism failure. In plain terms, the sandbox did not enforce a rule it should have. The two ratings disagree. The record scores 9.6 from the vector, while Chromium calls it Low, probably because it only helps an attacker who already holds a compromised renderer. Read both numbers, and do not pick one.
Either way the fix ships in the same Chrome update as the Critical ones, so there is no reason to treat it separately. The record does not flag the CVE as known exploited.
The record lists these weakness classes: CWE-269 (Improper Privilege Management), CWE-693 (Protection Mechanism Failure).
Quick check
Which severity should I use, 9.6 or Low?
Use neither alone. The 9.6 is a vector score. Chromium rates it Low because it needs a prior renderer compromise. You patch both the same way.
Sources
Last reviewed: 19 October 2026.
