CVE-2026-12016
published 2026-06-11CVE-2026-12016: Inappropriate implementation in DevTools in Google Chrome prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to…
PriorityP344high8.3CVSS 3.1
AVNACHPRNUIRSCCHIHAH
EPSS
0.23%
13.8th percentile
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)
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 149.0.7827.115 | 149.0.7827.115 | |
| chrome | >= 149.0.7827.115 < 149.0.7827.115 | 149.0.7827.115 | |
| chrome_desktop | — | — | |
| paloalto | prisma_browser | — | — |
CVSS provenance
nvdv3.18.3HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
vendor_redhat8.3HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Palo Alto
PAN-SA-2026-0010 Chromium and Prisma Browser: Monthly Vulnerability Update (July 2026)
vendor_paloalto·2026-07-08·CVSS 9.6
CVE-2026-10881 [CRITICAL] PAN-SA-2026-0010 Chromium and Prisma Browser: Monthly Vulnerability Update (July 2026)
PAN-SA-2026-0010 Chromium and Prisma Browser: Monthly Vulnerability Update (July 2026)
Palo Alto Networks incorporated the following Chromium security fixes into our products: https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01245939337.html https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0482630350.html https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01750511403.html https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01962725236.html https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html CVE Summary CVE-2026-10881 Out of bounds rea
Chrome
Stable Channel Update for Desktop: CVE-2026-12014
vendor_chrome·2026-06-11·CVSS 8.3
CVE-2026-12014 [HIGH] Stable Channel Update for Desktop: CVE-2026-12014
Stable Channel Update for Desktop
CVE-2026-12014: Use after free Cast. Reported by Google on 2026-05-19 [N/A][ 515463295 ] High CVE-2026-12015: Use after free Autofill
Reported by Google on 2026-05-21 [N/A][ 516482138 ] High CVE-2026-12016: Insufficient validation of untrusted input DevTools
Severity: high
Chrome
Stable Channel Update for Desktop: CVE-2026-12016
vendor_chrome·2026-06-11
CVE-2026-12016 [HIGH] Stable Channel Update for Desktop: CVE-2026-12016
Stable Channel Update for Desktop
CVE-2026-12016: Insufficient validation of untrusted input DevTools. Reported by Google on 2026-05-25 [N/A][ 516797143 ] High CVE-2026-12017: Insufficient validation of untrusted input Extensions
Reported by Google on 2026-05-26 [N/A][ 516808201 ] High CVE-2026-12018: Inappropriate implementation Mojo
Severity: high
Red Hat
chromium-browser: chromium-browser: Insufficient validation of untrusted input DevTools
vendor_redhat·2026-06-11·CVSS 8.3
CVE-2026-12016 [HIGH] CWE-501 chromium-browser: chromium-browser: Insufficient validation of untrusted input DevTools
chromium-browser: chromium-browser: Insufficient validation of untrusted input DevTools
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)
The following flaw was identified in the Chromium browser: Insufficient validation of untrusted input DevTools.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=516482138
Statement: Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
VulDB
Google Chrome up to 149.0.7827.103 DevTools sandbox (ID 516482 / EUVD-2026-36337)
vuldb·2026-06-13·CVSS 8.3
CVE-2026-12016 [HIGH] Google Chrome up to 149.0.7827.103 DevTools sandbox (ID 516482 / EUVD-2026-36337)
A vulnerability classified as critical has been found in Google Chrome. Affected by this issue is some unknown functionality of the component DevTools. The manipulation leads to sandbox issue.
This vulnerability is documented as CVE-2026-12016. The attack can be initiated remotely. There is not any exploit available.
It is recommended to upgrade the affected component.
GHSA
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 craft
ghsa_unreviewed·2026-06-12
CVE-2026-12016 [HIGH] CWE-20 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 craft
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)
No detection rules found.
No public exploits indexed.
Bugzilla
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-2
bugzilla·2026-06-22·CVSS 8.8
CVE-2026-12007 [HIGH] 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-2
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 ... chromium: various flaws [epel-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Discussion:
It's fixed in chromium-149.0.7827.114
Bugzilla
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-2
bugzilla·2026-06-22·CVSS 8.8
CVE-2026-12007 [HIGH] 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-2
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 ... chromium: various flaws [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Discussion:
It's fixed in chromium-149.0.7827.114
Bugzilla
CVE-2026-12016 chromium-browser: chromium-browser: Insufficient validation of untrusted input DevTools
bugzilla·2026-06-11·CVSS 8.3
CVE-2026-12016 [HIGH] CVE-2026-12016 chromium-browser: chromium-browser: Insufficient validation of untrusted input DevTools
CVE-2026-12016 chromium-browser: chromium-browser: Insufficient validation of untrusted input DevTools
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)
2026-06-11
Published