EUVD-2026-65887
GHSA-8jmw-56jj-3c63
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network delivery via crafted page (AV:N), no auth required (PR:N), victim must visit page (UI:R), scope unchanged by sandbox boundary (S:U), full CIA impact within renderer process.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Buffer overflow in V8 in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Remote code execution within the Chrome sandbox is possible in Google Chrome prior to 152.0.7977.65 via a stack-based buffer overflow in the V8 JavaScript engine, triggered by a crafted HTML page visited by an unpatched user. The vulnerability requires no authentication or elevated privileges from the victim - only that they visit an attacker-controlled page - and achieves arbitrary code execution within Chrome's renderer sandbox. …
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 only that the victim visit an attacker-controlled HTML page using a vulnerable version of Google Chrome (prior to 152.0.7977.65) - no special Chrome configuration, enabled features, or victim-side privileges are required, consistent with AV:N/AC:L/PR:N in the CVSS vector. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.8 score is driven by network accessibility (AV:N), low complexity (AC:L), no required privileges (PR:N), and full confidentiality, integrity, and availability impact within the affected scope - metrics that accurately reflect how easy it is to deliver the exploit. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers or compromises a domain and serves a crafted HTML page containing malicious JavaScript engineered to trigger the V8 stack buffer overflow. A victim using unpatched Chrome visits the page - perhaps via a phishing link, malvertising, or a compromised legitimate site - causing the overflow to corrupt stack control data and redirect V8 execution to attacker-controlled code within the Chrome renderer sandbox. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later; this is the vendor-confirmed fixed release per the stable channel advisory 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: issue mandatory patch notification to all users and verify Chrome deployment policies are current. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-121 – Stack-based Buffer Overflow
View allSame technique Stack Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today