EUVD-2026-50748
GHSA-p6vr-qm9c-fq9v
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Network delivery via malicious file with mandatory user interaction; DAC bypass yields only partial C/I with no availability or scope-change impact.
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
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Safe Browsing in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass discretionary access control via a malicious file. (Chromium security severity: Medium)
AnalysisAI
Safe Browsing in Google Chrome prior to 151.0.7922.72 fails to adequately validate untrusted input from a malicious file, allowing a remote attacker to bypass discretionary access control within the browser. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) confirms unauthenticated network delivery is viable but requires user interaction with the malicious file, limiting both automation and stealth. EPSS at 0.20% (11th percentile) and SSVC exploitation status of 'none' align with the absence of any public exploit or KEV listing, placing this firmly in a patch-and-monitor posture rather than an emergency response.
Technical ContextAI
Google Chrome's Safe Browsing feature is a client-side protection subsystem that inspects URLs, downloads, and files against threat intelligence feeds to warn users of potentially dangerous content. CWE-20 (Improper Input Validation) identifies the root cause: the Safe Browsing component does not sufficiently validate data originating from an untrusted file before acting on it, allowing an attacker-controlled input to influence an access control decision in an unintended way. The affected CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) covers all Chrome desktop instances across platforms (Windows, macOS, Linux) running versions prior to 151.0.7922.72. Because Safe Browsing is a default-on feature, no special configuration is required for the vulnerable code path to be reachable.
RemediationAI
The primary fix is upgrading Google Chrome to version 151.0.7922.72 or later, as released in the stable channel update documented at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Most consumer Chrome installations will receive this update automatically; enterprise administrators using Google Admin Console, Microsoft Intune, or similar MDM tooling should verify the patch has propagated across managed endpoints. As a compensating control where immediate patching is not operationally feasible, switching Safe Browsing to Enhanced Protection mode (rather than Standard) adds additional server-side telemetry checks that may reduce bypass effectiveness, though this does not eliminate the underlying vulnerability. Blocking execution of files from untrusted or external sources at the endpoint or email gateway level reduces the attack surface by limiting attacker-controlled file delivery. No side effects from the patch itself have been reported.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today