Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network delivery, high complexity (chained renderer compromise plus social engineering), no target-system privileges needed, user interaction required, scope change for sandbox escape with full CIA 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
Incorrect authorization in USB in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape via incorrect USB authorization in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox through a crafted HTML page combined with social engineering. The attack chain is multi-stage: the USB subsystem fails to correctly authorize renderer-process requests, enabling a scoped privilege escalation out of the sandbox (S:C in CVSS). …
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 two chained conditions: (1) the attacker must already have achieved code execution within the Chrome renderer process via a separate, independently exploited vulnerability - this is an explicit prerequisite stated in the CVE description, not an optional condition; and (2) social engineering must be used to facilitate the crafted HTML page interaction, confirmed by UI:R in the CVSS vector. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 8.3 (High) with S:C (scope change) correctly captures the sandbox-escape nature of this flaw, but the AC:H and UI:R modifiers are critical context: exploitation is not straightforward. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker controlling a malicious or compromised website first exploits a separate renderer-process vulnerability in a victim's Chrome browser to gain code execution within the sandboxed renderer. From that foothold, the attacker serves a crafted HTML page that manipulates the USB IPC channel and exploits the incorrect authorization logic to issue privileged USB requests the renderer should not be permitted to make, causing the browser process to execute attacker-controlled code outside the sandbox. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later; this is the vendor-confirmed patched release documented at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all Chrome installations across the organization and prepare rollout plan for version 152.0.7977.65 or later, prioritizing users with administrative access or handling sensitive data. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65777
GHSA-6x88-35m6-5r8v