EUVD-2026-50600
GHSA-gvh4-9j76-m35h
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects the mandatory renderer-compromise prerequisite; remaining metrics align with the vendor description and published vector.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
5DescriptionCVE.org
Side-channel information leakage in Autofill in Google Chrome prior to 151.0.7922.72 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
Side-channel information leakage in Chrome's Autofill component exposes cross-origin data to remote attackers who have already achieved renderer process compromise. All Chrome versions prior to 151.0.7922.72 are affected across all 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 two explicit preconditions: (1) the attacker must have already compromised the Chrome renderer process through a separate, independent vulnerability - this CVE is not a standalone attack vector; and (2) the victim user must interact with a crafted HTML page while the renderer compromise is active (UI:R per CVSS). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The published CVSS 4.3 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) materially overstates standalone exploitability: the description explicitly requires the attacker to have already compromised the renderer process, a significant prerequisite that PR:N and AC:L do not capture. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already established code execution within Chrome's renderer process - via a separate, prior renderer vulnerability - crafts a malicious HTML page that triggers the Autofill side-channel. By observing measurable behavioral differences (e.g., timing variations) in the Autofill subsystem while the compromised renderer interacts with cross-origin content, the attacker infers sensitive form field data from other origins loaded in the browser session. … |
| Remediation | Update Google Chrome to version 151.0.7922.72 or later, which contains the vendor-released patch for this vulnerability. … 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 allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today