EUVD-2026-34644
GHSA-2xcg-3jrg-6gj2
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds read in GWP-ASan in Google Chrome prior to 149.0.7827.53 allowed a local attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: Medium)
AnalysisAI
Out-of-bounds read in Chrome's GWP-ASan memory safety subsystem (versions prior to 149.0.7827.53) enables a local attacker to disclose potentially sensitive contents from process memory by delivering a malicious file to the target. The vulnerability carries a CVSS 6.5 Medium score with high confidentiality impact but no integrity or availability impact, consistent with a pure information-disclosure class. No public exploit code has been identified at time of analysis, EPSS exploitation probability is extremely low at 0.01% (1st percentile), and SSVC assessment confirms no known active exploitation, collectively indicating a low near-term threat priority despite the notable confidentiality impact rating.
Technical ContextAI
GWP-ASan (Guard With Probability AddressSanitizer) is a probabilistic, low-overhead heap memory-safety tool integrated directly into the Chrome browser process. It instruments a sampled subset of heap allocations by surrounding them with guard pages to detect out-of-bounds accesses and use-after-free conditions at runtime. CWE-125 (Out-of-Bounds Read) describes the root cause: a read operation that advances beyond the legitimate bounds of an allocated buffer, allowing the attacker to observe memory contents adjacent to or elsewhere within the process address space. In the context of GWP-ASan, the flaw is ironic - a memory-safety instrumentation layer itself contains a memory-safety defect. The affected CPE corresponds to Google Chrome versions prior to 149.0.7827.53 across desktop platforms.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later, as detailed in the official Stable Channel Update advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's built-in auto-update mechanism will deliver this patch to most users automatically; enterprise deployments managed via policy should verify fleet-wide rollout using Chrome Browser Cloud Management or equivalent tooling. No specific workarounds are documented in available references. If immediate patching is not feasible in managed environments, restricting users from opening untrusted or unexpected file types through endpoint DLP or application control policies can reduce the probability of triggering the vulnerable code path, though this does not eliminate the underlying vulnerability and carries usability trade-offs.
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today