CVE-2026-12027: Critical severity Google Chrome vulnerability
Inappropriate implementation in Headless 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)
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.7827.114
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-12007
- CVE-2026-12008
- CVE-2026-12009
- CVE-2026-12010
- CVE-2026-12011
- CVE-2026-12012
- CVE-2026-12014
- CVE-2026-12015
- CVE-2026-12016
- CVE-2026-12017
- CVE-2026-12018
- CVE-2026-12019
- CVE-2026-12020
- CVE-2026-12022
- CVE-2026-12023
- CVE-2026-12024
- CVE-2026-12025
- CVE-2026-12026
- CVE-2026-12028
- CVE-2026-12029
- CVE-2026-12030
- CVE-2026-12031
- CVE-2026-12032
- CVE-2026-12033
- CVE-2026-12034
- CVE-2026-12035
Frequently Asked Questions
What is the severity of CVE-2026-12027?
The severity of CVE-2026-12027 is critical with a CVSS score of 9.6.
How do I fix CVE-2026-12027?
To fix CVE-2026-12027, you should update Google Chrome to version 149.0.7827.115 or later.
What vulnerabilities are exploited in CVE-2026-12027?
CVE-2026-12027 allows a remote attacker to potentially perform a sandbox escape via a crafted HTML page.
What impact does CVE-2026-12027 have on users?
CVE-2026-12027 can potentially lead to unauthorized access to the user's system due to sandbox escape.
Which software is affected by CVE-2026-12027?
CVE-2026-12027 affects Google Chrome versions prior to 149.0.7827.115.