CVE-2026-12016: Inappropriate Implementation in DevTools in Google Chrome Prior to 149.0.7827.115 Allows Sandbox Escape
A NVD · · CVE-2026-12016
Admiralty grading (A–F · 1–6)
Source reliability
- A Completely reliable
- B Usually reliable
- C Fairly reliable
- D Not usually reliable
- E Unreliable
- F Cannot be judged
Information credibility
- 1 Confirmed
- 2 Probably true
- 3 Possibly true
- 4 Doubtful
- 5 Improbable
- 6 Cannot be judged
NATO Admiralty (AJP-2.1) grades confidence, independent of the risk score. Cross-source corroboration isn't tracked for non-CVE news, so single-source items are capped at a lower credibility number; a low number does not imply low quality.
Key metrics
- EPSS
- 0%
Key insight
A sandbox escape in Chrome DevTools requires a compromised renderer process but enables elevated attack capabilities against targeted developers or technical users.
Description
CVE-2026-12016 describes an inappropriate implementation in the DevTools component of Google Chrome (versions prior to 149.0.7827.115). A remote attacker who has already compromised the renderer process can potentially perform a sandbox escape via a crafted HTML page. The Chromium security severity is rated High. This is a multi-stage attack: initial renderer compromise is required, after which the vulnerability enables sandbox escape with elevated privileges.
Risk score
- cvss base
- 0.00
- kev bonus
- 0.00
- epss bonus
- 0.00
- poc bonus
- 0.00
- raw before weight
- 0.00
- industry weight
- 1.21
- freshness factor
- 1.00
- exploitability factor
- 1.00
- days old
- 0.00
- vendor mismatch penalty
- 0.00
Path: operational