Skip to main content

Google Chrome EUVDEUVD-2026-50913

| CVE-2026-17987 CRITICAL
Improper Input Validation (CWE-20)
2026-07-30 Chrome GHSA-qw96-7rhh-gvmj
Critical
Disputed · 9.6 Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise renderer via separate bug
  2. Delivery
    Deliver crafted PDF to victim
  3. Exploit
    Victim renders PDF in Notifications path
  4. Execution
    Trigger improper input validation
  5. Persist
    Escape sandbox to browser process
  6. Impact
    Execute code outside sandbox

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation requires the attacker to have ALREADY compromised the renderer process - this is a sandbox-escape primitive, not an initial-access bug - plus user interaction to render a crafted PDF file (CVSS UI:R). The specific trigger is untrusted input processed by the Notifications component via a malicious PDF. Limiting factors: the mandatory prior renderer compromise, the requirement that the victim open/render the attacker's PDF, and applicability only to Chrome versions before 151.0.7922.72; SSVC records Exploitation: none and the bug is not automatable, so it is not usable for unauthenticated one-shot remote takeover despite the PR:N in the CVSS vector.

Impact

The signals conflict sharply and must be read together. The CVSS 3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) looks critical, but it does not reflect the description's explicit precondition that the attacker must have ALREADY compromised the renderer process - this is a second-stage sandbox-escape primitive, not a standalone remote takeover, so AC:L/PR:N materially overstates ease of exploitation. Corroborating this, Chromium itself rated the security severity Low, CISA SSVC records Exploitation: none and Automatable: no (though Technical Impact: total), and EPSS is only 0.16% (6th percentile). There is no KEV listing and no public exploit identified. Net: this is a chainable component of a full exploit rather than a directly weaponizable single bug - real-world priority is moderate for defenders who patch Chrome on the normal cycle, higher only for high-value targets facing sophisticated exploit chains.

Exploit ScenarioDerived

An attacker first uses a separate renderer-level bug to gain code execution inside Chrome's sandboxed renderer, then lures the victim to open or render a crafted PDF that abuses the Notifications input-validation flaw to escape the sandbox into the browser process. No public exploit is identified at time of analysis, and the chain depends on user interaction (UI:R) plus a pre-existing renderer compromise, making it a targeted rather than opportunistic scenario.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 30, 2026

Sandbox escape in Google Chrome before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox by feeding a crafted PDF through the Notifications component, which insufficiently validates untrusted input (CWE-20). Full technical impact (SSVC: total) means a successful escape yields code execution outside the constrained renderer. Despite a 9.6 CVSS, Chromium rated this Low severity, EPSS is 0.16%, and there is no public exploit identified at time of analysis.

RemediationAI

Vendor-released patch: update Google Chrome to 151.0.7922.72 or later via the Stable Channel; a patch is available from the vendor per the Chrome release advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Restart the browser after updating so the new binary is loaded, and confirm the version at chrome://settings/help. As a compensating control until patching completes, restrict handling of untrusted PDFs - for example, route external PDFs through Chrome's default viewer only from trusted sources, or use enterprise policy to disable inline PDF rendering (AlwaysOpenPdfExternally) so crafted PDFs are handed to an external reader instead of Chrome's renderer; the trade-off is degraded in-browser PDF usability. Because exploitation requires a prior renderer compromise, keeping Chrome fully updated (which also closes the renderer-level bugs needed to reach this one) is the most effective mitigation.

Affected VersionsENISA

Chrome 151.0.7922.72 <151.0.7922.72

Affected Packages

euvd chrome fix: 151.0.7922.72

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw lives in Chrome's Notifications handling of data originating from a crafted PDF, an area that processes content already inside the browser's multi-process security model. Chrome isolates untrusted web/PDF rendering in a sandboxed renderer process; a sandbox escape (CVSS S:C, scope changed) crosses that trust boundary into the more-privileged browser process. The root cause is CWE-20 (Improper Input Validation): untrusted input reaching the Notifications logic is not sufficiently validated, enabling the renderer-to-browser boundary to be violated. The single affected product per CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* across all versions prior to the fix.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Sources disagree (Low–Critical)
Vendor (Chrome) PRIMARY 9.6 CRITICAL
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
vuln.today AI 8.3 HIGH

Requires a prior renderer compromise plus a crafted PDF, so AC:H and UI:R; the sandbox escape crosses a trust boundary (S:C) with full impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
SUSE CRITICAL
Red Hat 4.3 LOW

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Chrome

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Jul 30, 2026 - 20:37 NVD
9.6 (None) 9.6 (CRITICAL)
Patch available
Jul 30, 2026 - 02:02 EUVD
CVE Published
Jul 30, 2026 - 00:25 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 30, 2026 - 00:25 cve.org
CRITICAL 9.6

DescriptionCVE.org

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)

Executive ViewAI

Why It Matters

Google Chrome versions before 151.0.7922.72 contain a critical sandbox escape (CVE-2026-17987, CVSS 9.6) that enables unrestricted code execution through maliciously crafted PDFs. While the vulnerability carries severe technical impact, real-world exploitation risk remains low at 0.2% EPSS with no public exploit code identified, allowing planned patch deployment without emergency response mobilization.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Ubiquitous
Chrome is the most widely deployed desktop browser worldwide
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +48
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
SUSE Package Hub 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy