CVE-2026-12016: Input Validation
Chromium: CVE-2026-12016 Insufficient validation of untrusted input DevTools
Other sources
Inappropriate implementation in DevTools in Google Chrome prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
— MITRE
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 149.0.4022.69 - Upgrade
Upgrade
Chromium/Google Chrome (DevTools)to a version that resolves this vulnerability.Fixed in 149.0.7827.115
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-76033
- CVE-2026-12462
- CVE-2026-12025
- CVE-2026-76018
- CVE-2026-76023
- CVE-2026-11701
- CVE-2026-11664
- CVE-2026-76022
- CVE-2026-76045
- CVE-2026-19558
- CVE-2026-13027
- CVE-2026-17693
- CVE-2026-15777
- CVE-2026-19144
- CVE-2026-11666
- CVE-2026-10949
- CVE-2026-11658
- CVE-2026-11652
- CVE-2026-19559
- CVE-2026-10938
- CVE-2026-9124
- CVE-2026-9951
- CVE-2026-7991
- CVE-2026-11681
- CVE-2026-19145
- CVE-2026-13034
- CVE-2026-19165
Frequently Asked Questions
What is the severity of CVE-2026-12016?
CVE-2026-12016 has a high severity rating of 8.3 according to the CVSS 3.1 metrics.
How do I fix CVE-2026-12016?
To fix CVE-2026-12016, update Google Chrome to version 149.0.7827.115 or later.
What impact does CVE-2026-12016 have on my system?
CVE-2026-12016 could allow a remote attacker to perform a sandbox escape if the renderer process is compromised through a crafted HTML page.
What software is affected by CVE-2026-12016?
CVE-2026-12016 affects Google Chrome versions prior to 149.0.7827.115.
How was CVE-2026-12016 introduced?
CVE-2026-12016 was introduced due to an inappropriate implementation in the DevTools component of Google Chrome.