EUVD-2026-65975
GHSA-8h5q-977g-xqf2
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attacker delivers exploit remotely via extension (AV:N, PR:N); mandatory social engineering step sets UI:R; sandbox containment with full internal impact justifies S:U with C:H/I:H/A:H.
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
3DescriptionCVE.org
Use after free in DevTools in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to execute arbitrary code inside the sandbox via a crafted Chrome extension. (Chromium security severity: Medium)
AnalysisAI
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) allows a remote attacker to execute arbitrary code within the browser's renderer sandbox. Exploitation requires the victim to be socially engineered into installing and activating a crafted Chrome extension, making this a user-interaction-dependent attack rather than a passive drive-by. …
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 be actively socially engineered into installing a crafted Chrome extension - this is not a passive, zero-click drive-by vulnerability. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.8 score reflects the full C:H/I:H/A:H triad, but the UI:R (user interaction required) component is critical context: this is not a passive or autonomous exploit. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker packages a use-after-free trigger into a Chrome extension and distributes it via a spear-phishing campaign - for example, posing as a required corporate productivity tool or a browser update helper. Once the victim installs the extension and it interacts with the DevTools component, the freed memory region is reclaimed with attacker-controlled data, redirecting execution to shellcode that runs within Chrome's renderer sandbox. … |
| Remediation | Upgrade Google Chrome to version 152.0.7977.65 or later immediately, as documented in the stable channel update 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, communicate the vulnerability to all users and enforce a temporary policy restricting extension installations from untrusted sources pending patch deployment. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-416 – Use After Free
View allSame technique Use After Free
View allShare
External POC / Exploit Code
Leaving vuln.today