EUVD-2026-40563
GHSA-96cx-548v-f4qx
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-delivered via crafted HTML (AV:N), AC:H for mandatory prior renderer compromise; C:H for process memory read; no integrity or availability impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Process memory disclosure in Google Chrome's ANGLE graphics abstraction layer (versions prior to 150.0.7871.47) enables a renderer-compromised attacker to read potentially sensitive data from process memory via a crafted HTML page. This is a post-exploitation, second-stage vulnerability: it cannot be triggered without a prior renderer process compromise, functioning as a chaining component rather than a standalone entry point. …
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 has two mandatory prerequisites: (1) the attacker must have already compromised the Chrome renderer process through a separate, unrelated vulnerability - this is the condition encoded in the AC:H CVSS metric and explicitly stated in the CVE description; and (2) the victim user must visit a crafted HTML page (UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N) scores 5.3, with AC:H accurately reflecting the hard prerequisite of prior renderer compromise - the single largest real-world risk limiter. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already exploited a separate Chrome renderer vulnerability (e.g., a V8 JavaScript engine type confusion) pivots to delivering a crafted HTML page that triggers the ANGLE input validation flaw, causing the GPU abstraction layer to return out-of-bounds memory contents back to the attacker-controlled renderer. The disclosed memory could include sensitive data such as authentication tokens, decrypted content, or cryptographic keys from co-located process memory. … |
| Remediation | The primary and definitive fix is upgrading Google Chrome to version 150.0.7871.47 or later, as documented in the Google stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today