EUVD-2026-65814
GHSA-j524-j2m2-2mcv
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-delivered UAF via WebRTC traffic with no auth required, but AC:H reflects heap-shaping complexity; sandbox containment keeps scope unchanged with full renderer-level C/I/A.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in WebRTC in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via crafted network traffic. (Chromium security severity: High)
AnalysisAI
Remote code execution inside the Chrome sandbox is achievable via a use-after-free in the WebRTC component of Google Chrome prior to 152.0.7977.65, exploitable by an unauthenticated remote attacker through crafted network traffic. The flaw requires high attack complexity (AC:H), constraining opportunistic mass exploitation, and code execution is limited to within the Chrome renderer sandbox, reducing but not eliminating post-exploitation impact. …
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 | The victim must be running Google Chrome prior to version 152.0.7977.65 and must have an active WebRTC session processing attacker-controlled network traffic - this occurs when visiting a page that initiates a WebRTC connection (peer-to-peer call, data channel, or video conferencing) with an endpoint the attacker controls or can inject traffic into. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects severe potential impact if exploited, but the AC:H metric is a meaningful real-world constraint - UAF exploitation in modern Chromium typically requires precise heap-shaping, timing control, or race-condition triggering, making reliable exploitation considerably harder than AC:L bugs. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker establishes or hijacks a WebRTC session with a victim running an unpatched version of Chrome - for example, by luring the victim to a malicious web page that initiates a WebRTC data or media channel. The attacker then sends a sequence of specially crafted RTP or RTCP packets designed to trigger the use-after-free condition in Chrome's WebRTC processing path, corrupt heap memory, and redirect execution to attacker-controlled code. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later, as documented in the Chrome Stable Channel Update advisory at 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, inventory all Chrome instances in your organization and establish baseline version compliance. …
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