CVE-2026-14120 is a flaw (CVSS 9.6 in the record) in DevTools in Google Chrome before 150.0.7871.47. An inappropriate implementation could let an attacker who compromised the renderer escape the sandbox via a crafted page. Chromium rates it Low. 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. 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
Chromium uses the phrase inappropriate implementation for a bug where a feature does not behave as designed. The record maps it to improper input validation and protection mechanism failure. DevTools has deep access to the browser, so it needs careful checks on what a page can reach.
As with the rest of this release, the vector gives 9.6, Chromium says Low, and the attacker needs a compromised renderer first. Developers who run DevTools often should be sure the browser they use for it is also updated. The record does not flag the CVE as known exploited.
The record lists these weakness classes: CWE-20 (Improper Input Validation), CWE-693 (Protection Mechanism Failure).
Quick check
Do I have to be using DevTools to be exposed?
The record does not say so. It lists the component and the fixed version, so update the browser regardless.
Sources
Last reviewed: 19 October 2026.
