EUVD-2026-65765
GHSA-95jm-f7jf-r5vr
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network delivery via crafted page; AC:H reflects mandatory renderer pre-compromise; scope change and full C/I/A impact confirmed by sandbox escape nature.
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 Sandbox in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has first compromised the renderer process to break out of Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. Rooted in CWE-863 (Incorrect Authorization), the Chrome sandbox fails to correctly enforce permission checks on requests originating from a compromised renderer, permitting privilege escalation beyond the sandbox boundary. …
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 the victim to actively visit a crafted HTML page in a vulnerable version of Chrome (any version prior to 152.0.7977.65), satisfying the UI:R requirement. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score of 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects the potential for full system compromise with scope change, but the AC:H and UI:R metrics indicate meaningful exploitation friction: the attacker must both socially engineer a page visit and first achieve renderer compromise. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page that first triggers a renderer process vulnerability to achieve renderer compromise, then leverages the incorrect sandbox authorization flaw in CVE-2026-79218 to escape Chrome's sandbox and execute code in the context of the logged-in OS user. The victim must visit the malicious page (UI:R), at which point the two-stage chain - renderer compromise followed by sandbox escape - executes silently. … |
| Remediation | Vendor-released patch: Chrome 152.0.7977.65. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, issue an urgent patch notification to all stakeholders and begin inventory of Chrome installations across managed and unmanaged endpoints. …
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