EUVD-2026-40774
GHSA-qp3w-hw9g-27h5
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Requires a pre-compromised renderer (modeled as PR:L) plus added exploitation effort and user navigation, so AC:H and UI:R; heap corruption yields total impact (C/I/A:H).
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Heap buffer overflow in WebNN in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Heap corruption in Google Chrome's WebNN (Web Neural Network API) implementation on Windows, fixed in 150.0.7871.47, lets an attacker who has already compromised the renderer process trigger a heap buffer overflow via a crafted HTML page and potentially escalate beyond the sandbox. Chromium's own security team rated this Low severity, while NVD scores it 8.8; EPSS is low at 0.19% (9th percentile) and there is no public exploit identified at time of analysis. …
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 that the attacker has ALREADY compromised the Chrome renderer process - this is the concrete prerequisite stated in the CVE description and it is the primary limiting factor; the bug cannot be triggered from a fresh, uncompromised browser. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals conflict and should be weighed carefully. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already gained code execution inside the Chrome renderer (for example by chaining an earlier renderer bug) drives the victim's browser to a crafted HTML page that feeds the WebNN API malformed graph input, triggering a heap buffer overflow. The resulting heap corruption can be groomed toward controlled memory writes to strengthen a sandbox escape. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on Windows via the Stable channel update described at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html, then relaunch the browser to apply it - this is the primary and complete fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Windows systems running Chrome and document current versions; Within 7 days: Deploy Chrome 150.0.7871.47 or later via endpoint management tools; Within 30 days: Verify patch deployment completion and confirm all Chrome instances are updated.
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Important| 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