CVE-2026-12016: Input Validation

Published May 25, 2026
·
Updated

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

Google

Affected Software

8 affected componentsFixes available
Google Chrome<149.0.7827.115
Microsoft Edge<149.0.4022.69
Google Chrome<149.0.7827.114
149.0.7827.114
All of the following
Google Chrome<149.0.7827.115
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
Microsoft Edge (Chromium-based)<149.0.4022.69
149.0.4022.69

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 149.0.7827.114
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 149.0.4022.69
  3. Upgrade

    Upgrade Chromium/Google Chrome (DevTools) to a version that resolves this vulnerability.

    Fixed in 149.0.7827.115

Event History

May 25, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Jun 11, 2026
CVE Published
via MITRE·08:48 PM
Data Sourced
via MITRE·08:48 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Jun 15, 2026
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

How do I fix CVE-2026-12016?

To fix CVE-2026-12016, update Google Chrome to version 149.0.7827.115 or later.

3

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.

4

What software is affected by CVE-2026-12016?

CVE-2026-12016 affects Google Chrome versions prior to 149.0.7827.115.

5

How was CVE-2026-12016 introduced?

CVE-2026-12016 was introduced due to an inappropriate implementation in the DevTools component of Google Chrome.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203