CVE-2026-12024: Medium severity Google Google Chrome vulnerability
Insufficient policy enforcement in DevTools in Google Chrome prior to 149.0.7827.115 allowed a remote attacker to bypass same origin policy 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-12025
- CVE-2026-12026
- CVE-2026-12027
- 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-12024?
The severity of CVE-2026-12024 is rated as medium with a CVSS score of 6.5.
How can I fix CVE-2026-12024?
To fix CVE-2026-12024, ensure that you update Google Chrome to version 149.0.7827.115 or later.
What vulnerabilities does CVE-2026-12024 address in Google Chrome?
CVE-2026-12024 addresses the issue of insufficient policy enforcement in DevTools that allows remote attackers to bypass the same origin policy.
Who is affected by CVE-2026-12024?
Users of Google Chrome prior to version 149.0.7827.115 are affected by CVE-2026-12024.
What type of attacks can CVE-2026-12024 potentially allow?
CVE-2026-12024 can potentially allow a remote attacker to bypass the same origin policy via a crafted HTML page.