EUVD-2026-66027
GHSA-6jm2-4q47-8grp
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-delivered via crafted page (AV:N), race condition requires precise timing (AC:H), no auth needed (PR:N), user must visit page (UI:R), impact limited to information disclosure with no integrity or availability effect.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Race condition in Editing in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Race condition in Google Chrome's Editing component prior to version 152.0.7977.65 enables remote attackers who successfully socially engineer a victim to visit a crafted HTML page to extract sensitive information from the browser. The CVSS vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N) shows the attack is network-delivered but requires high complexity timing and explicit user interaction, limiting real-world exploitability. …
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 two concrete preconditions: the victim must be running Google Chrome prior to version 152.0.7977.65, and must be successfully socially engineered into visiting an attacker-controlled crafted HTML page (UI:R per CVSS). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS Medium score of 5.3 is driven primarily by a High confidentiality impact, but the remaining metrics substantially constrain real-world exploitability: AC:H demands precise race-condition timing that is inherently unreliable, and UI:R means the attack cannot proceed without a victim actively visiting the attacker's page. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a malicious HTML page that embeds JavaScript designed to trigger a precise timing window in Chrome's Editing component - for example, by rapidly toggling editable regions while racing a read operation against a security boundary check. The victim is lured to the page via a phishing email or malicious advertisement, loading it in an unpatched Chrome browser and allowing the attacker to potentially extract sensitive in-browser data such as content from cross-origin frames or protected memory regions. … |
| Remediation | The primary fix is upgrading Google Chrome to version 152.0.7977.65 or later, available through Chrome's built-in auto-update mechanism or 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. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today