Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
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: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds read in Dawn in Google Chrome on Windows prior to 149.0.7827.103 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Out-of-bounds read in Dawn, Chrome's WebGPU graphics API layer, on Windows enables unauthenticated remote attackers to leak cross-origin data by serving a crafted HTML page. Affected versions of Google Chrome on Windows are all releases prior to 149.0.7827.103. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) confirms this is a network-exploitable, low-complexity information disclosure with no authentication requirement - limited only by the need for a user to visit the attacker-controlled page. No public exploit code or CISA KEV listing has been identified at time of analysis.
Technical ContextAI
Dawn is Google's open-source, cross-platform graphics API abstraction layer used in Chromium to implement the WebGPU standard. CWE-125 (Out-of-bounds Read) describes the root cause: the Dawn component reads beyond the boundary of an allocated memory buffer. In a browser renderer context, this class of flaw can expose memory contents belonging to a different security origin - violating the Same-Origin Policy - because renderer memory may contain data from multiple loaded resources. The vulnerability is scoped to Chrome on Windows specifically (per the NVD description), suggesting the OOB condition may be triggered by platform-specific graphics driver interactions or memory layout differences. The CVSS Scope:Unchanged (S:U) rating indicates the impact is confined to the renderer process itself rather than escaping to the OS or other processes.
RemediationAI
The primary fix is to update Google Chrome to version 149.0.7827.103 or later on Windows - this is a vendor-released patch confirmed by the Chrome stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html. Chrome's auto-update mechanism should handle delivery for most managed and consumer deployments; administrators should verify fleet compliance via endpoint management tooling. As a compensating control pending patch deployment, organizations can restrict access to untrusted external web content via proxy policy or browser isolation solutions, though this carries operational trade-offs for general browsing workflows. Disabling or restricting WebGPU via Chrome enterprise policy (WebGpuEnabled) would also reduce Dawn attack surface, but will break sites relying on WebGPU and should be tested before broad deployment.
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-35265
GHSA-5mhg-rh4j-h587