CVE-2026-17987: Insufficient validation of untrusted input in Notifications

Published Jun 4, 2026
·
Updated

Chromium: CVE-2026-17987 Insufficient validation of untrusted input in Notifications

Other sources

Insufficient validation of untrusted input in Notifications in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted PDF file. (Chromium security severity: Low)

— NVD

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

5 affected componentsFixes available
Google Google Chrome<151.0.7922.72
Google Chrome<151.0.7922.71
151.0.7922.71
Microsoft Edge (Chromium-based)<151.0.4129.59
151.0.4129.59
Microsoft Edge<151.0.4129.59
Google Chrome<151.0.7922.72

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 151.0.7922.71
  2. Upgrade

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

    Fixed in 151.0.4129.59
  3. Upgrade

    Upgrade Chromium / Google Chrome (Notifications PDF sandbox escape fix) to a version that resolves this vulnerability.

    Fixed in 151.0.7922.72

Event History

Jun 4, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Jul 30, 2026
CVE Published
via MITRE·12:25 AM
Data Sourced
via MITRE·12:25 AM
DescriptionWeakness
Data Sourced
via NVD·01:17 AM
DescriptionSeverityWeaknessAffected Software
Jul 31, 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-17987?

The severity of CVE-2026-17987 is rated critical with a CVSS score of 9.6.

2

How do I fix CVE-2026-17987?

To fix CVE-2026-17987, update Google Chrome to version 151.0.7922.72 or later.

3

What systems are affected by CVE-2026-17987?

CVE-2026-17987 affects Google Chrome prior to version 151.0.7922.72 and Chromium-based Microsoft Edge browsers.

4

What kind of risk does CVE-2026-17987 pose?

CVE-2026-17987 poses a risk of potential sandbox escape by a remote attacker who compromises the renderer process.

5

How can attackers exploit CVE-2026-17987?

Attackers can exploit CVE-2026-17987 by tricking the browser into insufficiently validating untrusted input in Notifications.

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