Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
AC:H reflects mandatory renderer-process compromise prerequisite; S:C reflects cross-origin boundary violation; PR:N as no additional auth is needed beyond the renderer foothold.
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionNVD
Inappropriate implementation in Autofill in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Cross-origin data leakage in Google Chrome's Autofill implementation allows a remote attacker who has already achieved renderer process compromise to exfiltrate sensitive cross-origin data via a specially crafted HTML page. Affected versions include all Chrome releases prior to 149.0.7827.197; the flaw was reported by the Chrome security team and rated High severity by Chromium. …
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 sequential conditions to both be satisfied: first, the attacker must have already compromised the Chrome renderer process via a separate, unrelated vulnerability - this is a substantial prerequisite that limits exploitation to sophisticated, multi-stage attack chains. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N scores 6.5 (Medium), but several signals indicate the real-world exploitability is considerably lower than a naive CVSS reading suggests. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has separately exploited a renderer process vulnerability in Chrome (such as a V8 engine flaw) uses that foothold to load a crafted HTML page designed to abuse the Autofill implementation boundary; the Autofill subsystem, operating with insufficient origin enforcement, exposes data belonging to a cross-origin context back to the attacker-controlled renderer, enabling exfiltration of sensitive autofill-populated values such as passwords, payment card data, or personal information stored by the browser. No public proof-of-concept for this specific chained attack has been identified at time of analysis. |
| Remediation | Update Google Chrome to version 149.0.7827.197 or later immediately via the Chrome menu → Help → About Google Chrome, or via enterprise deployment tools using the vendor's stable channel. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-346 – Origin Validation Error
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-39037
GHSA-3mjj-7mcj-gxwq