EUVD-2026-50586
GHSA-5563-95wf-5c3x
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H because exploitation depends on a prior renderer compromise and crafted content; UI:R and S:C reflect victim interaction and the sandbox-boundary escape; full C/I/A impact on escape.
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:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in DevTools 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: Medium)
AnalysisAI
Sandbox escape in Google Chrome's DevTools (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the sandbox and gain broader host access via a crafted HTML page. It stems from insufficient validation of untrusted input (CWE-20) and requires user interaction plus a pre-existing renderer foothold, so it functions as a second-stage exploit rather than a standalone entry point. …
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, separate exploit) - this is the explicit precondition stated in the CVE, not an optional detail. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals here conflict and must be weighed together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first uses a separate renderer exploit (e.g., a JavaScript engine bug) to gain code execution inside Chrome's sandboxed renderer when a victim visits a malicious site. Leveraging this foothold, the attacker serves a crafted HTML page that abuses the DevTools input-validation flaw to escape the sandbox and execute in the higher-privilege browser context. … |
| Remediation | Vendor-released patch: update Google Chrome to 151.0.7922.72 or later via the stable channel, as announced at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html; restart the browser to ensure the update is applied since Chrome staging can leave older processes running. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, deploy Google Chrome 151.0.7922.72 or later to all user endpoints via MDM or patch management, prioritizing systems accessing sensitive applications. …
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