EUVD-2026-65775
GHSA-v4v8-rm8r-mf7f
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network delivery requires user interaction and precise race-condition timing (AC:H); sandbox escape justifies S:C and full C/I/A:H 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
Race condition in ReadAloud 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 HTML page. (Chromium security severity: High)
AnalysisAI
Race condition in Chrome's ReadAloud component allows remote code execution inside the browser sandbox when a user is socially engineered into visiting a crafted HTML page. Affected are all Google Chrome builds prior to 152.0.7977.65 across desktop platforms. …
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 target user to visit a crafted HTML page, meaning successful social engineering (phishing, malvertising, or drive-by via a compromised trusted site) is a hard prerequisite - reflected in CVSS UI:R. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 8.3 reflects a serious but practically constrained threat: AV:N confirms internet-reachable delivery, but AC:H acknowledges that race condition exploitation requires precise timing and is difficult to trigger reliably. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page that, when rendered by Chrome's ReadAloud component, triggers a race condition between two concurrent execution paths sharing unsynchronized state. The attacker distributes the link via phishing or malvertising to lure a target into visiting the page, after which the race condition is won to corrupt or redirect execution flow, achieving arbitrary code execution within the Chrome renderer sandbox - and potentially escaping it given the S:C metric. |
| Remediation | The primary fix is to upgrade Google Chrome to version 152.0.7977.65 or later, as confirmed by the vendor's 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: Notify users of the patch availability and enforce update initiation; verify that your Chrome update distribution mechanisms (auto-update, MDM, or Group Policy) are properly configured. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-362 – Race Condition
View allSame technique Race Condition
View allShare
External POC / Exploit Code
Leaving vuln.today