EUVD-2026-50786
GHSA-36fh-9j3c-fp3f
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Attacker must first control the renderer, so PR:H; AC:H and UI:R reflect chaining plus a crafted page; scope changes on sandbox escape with full host impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Network 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 HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome's Network component before 151.0.7922.72 allows a remote attacker who has already compromised the renderer process to break out of the sandbox and gain broader access on the host via a crafted HTML page. Rated High by Chromium and scored CVSS 8.3, it is a second-stage bug that must be chained with an initial renderer exploit rather than exploited in isolation. …
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 that the attacker has ALREADY compromised the Chrome renderer process (a prior renderer exploit is a hard prerequisite named directly in the description), plus user interaction (UI:R) in the form of the victim loading a crafted HTML page, and the affected Chrome version must be prior to 151.0.7922.72. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are mixed and should be read together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first compromises the Chrome renderer with a separate memory-corruption or logic bug (for example by luring a user to a malicious site), then serves a crafted HTML page whose renderer-side code sends malformed input to the Network service to escape the sandbox and gain code execution outside the renderer's constraints. No public exploit is identified at time of analysis, and the high attack complexity plus required renderer foothold make this a targeted, chained operation rather than commodity attack. |
| Remediation | Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on every desktop platform, then fully restart the browser so all renderer and network processes reload the patched code - Chrome auto-updates but the fix does not take effect until relaunch. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify and catalog all Chrome installations across corporate infrastructure, noting versions currently deployed and prioritizing systems exposed to untrusted web content. …
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