EUVD-2026-65885
GHSA-qg44-f5xj-9rhx
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Network-delivered via crafted page (AV:N); race condition plus renderer pre-compromise raises complexity (AC:H); no host credentials needed (PR:N); user must visit page (UI:R); only partial confidentiality loss, no integrity or availability impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Race condition in Payments in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Cross-origin data leakage in Google Chrome's Payments subsystem, affecting all versions prior to 152.0.7977.65, stems from a TOCTOU race condition exploitable by an attacker who has already compromised the renderer process. By delivering a crafted HTML page, the attacker can race the Payments component to read data across origin boundaries, violating the Same-Origin Policy. …
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 compounding preconditions: first, the attacker must already have compromised the Chrome renderer process (e.g., via a separate renderer vulnerability), and second, the user must visit a crafted HTML page that exercises the Payments subsystem, providing the UI:R interaction. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS base score of 3.1 (Low) is consistent with the constrained exploitation prerequisites: AC:H reflects both the race condition timing requirement and the need for a pre-compromised renderer, while C:L limits impact to partial confidentiality loss with no integrity or availability impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first compromises a Chrome renderer process - for example via a separate memory-corruption bug in a content parser - then serves a crafted HTML page that triggers concurrent operations in the Payments subsystem. By winning the race between the time-of-check and time-of-use, the attacker reads data belonging to a cross-origin context, potentially leaking payment form data, authentication tokens, or other sensitive page content from a different origin. … |
| Remediation | Vendor-released patch: Google Chrome 152.0.7977.65. … 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