Severity by source
Sources disagree (Medium–Critical)AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
Description states adjacent malicious network traffic (AV:A) with no auth or interaction (PR:N/UI:N); a sandbox escape crosses a trust boundary (S:C) with partial, not total, impact (C/I/A:L).
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
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in WebUI in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to potentially perform a sandbox escape via malicious network traffic. (Chromium security severity: Medium)
AnalysisAI
Sandbox escape in Google Chrome desktop before 151.0.7922.72 stems from insufficient validation of untrusted input in a WebUI component, letting a remote attacker on the same network segment potentially break out of the renderer sandbox via malicious network traffic. Google rates the Chromium severity as Medium and vendor-tagged intelligence flags it as 'Potential RCE'; a vendor patch is available, but no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires (1) an unpatched Chrome build prior to 151.0.7922.72, (2) an adjacent-network position per CVSS AV:A - the attacker must reach the victim over the local/adjacent network (same LAN/broadcast domain or link-local scope), not the open internet, and (3) delivery of malicious network traffic that reaches the vulnerable WebUI component whose insufficient input validation is the flaw. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are consistent and point to moderate, not urgent, risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has gained a foothold on the same local network segment (e.g., a compromised device on a corporate LAN or shared Wi-Fi) sends crafted malicious network traffic that reaches a vulnerable WebUI surface in an unpatched Chrome instance. Exploiting the improper input validation, the attacker attempts to escape the renderer sandbox to gain higher-privilege execution. … |
| Remediation | Vendor-released patch: Chrome 151.0.7922.72 - upgrade to that Stable channel build or later on all desktop platforms, then fully relaunch the browser so the new binary loads (Chrome staged updates do not take effect until restart). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, notify IT and end-user groups of the required patch and audit Chrome desktop deployment scope across the organization. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
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
EUVD-2026-50637
GHSA-4g93-9mx8-6qjj