EUVD-2026-34621
GHSA-5r68-3wfw-rm9w
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 Input in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Out-of-bounds read in the Input component of Google Chrome on Linux (all versions prior to 149.0.7827.53) exposes potentially sensitive process memory to remote attackers. Exploitation requires delivering a crafted HTML page and inducing a Linux user to visit it (CVSS UI:R), after which the browser's Input handler reads beyond allocated buffer bounds, leaking in-memory data. No public exploit has been identified at time of analysis, EPSS sits at 0.03% (11th percentile) indicating low current exploitation probability, and there is no CISA KEV listing - though the High confidentiality impact (C:H) warrants timely patching given Chrome's broad deployment on Linux.
Technical ContextAI
The vulnerability is classified under CWE-125 (Out-of-bounds Read), a memory safety flaw where a read operation accesses memory beyond the intended buffer boundary. It is specifically located in Chrome's Input subsystem on Linux, suggesting the defect may be tied to platform-specific input event handling or Linux-specific IPC/input dispatch code paths within the Chromium codebase. Although the tags include 'Buffer Overflow,' the CWE and description are consistent with a read-only overreach rather than a write primitive, meaning the attacker gains visibility into process memory rather than control flow. Chromium's multi-process sandboxed architecture may constrain what memory is accessible from the renderer context, but the CVSS C:H rating indicates meaningful sensitive data - potentially session tokens, cached credentials, or cross-origin page content - could be disclosed. The Chromium issue tracker reference (issues.chromium.org/issues/501862016) is the upstream bug report; the fixed release is Chrome stable 149.0.7827.53 per ENISA EUVD-2026-34621.
RemediationAI
The primary fix is to update Google Chrome on Linux to version 149.0.7827.53 or later - this is the vendor-released patch confirmed by the stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprise deployments managed via Google Admin or MDM should push this update through their software management pipeline immediately. For environments where immediate patching is operationally infeasible, compensating controls include restricting Chrome users to an allowlisted set of trusted URLs via enterprise web filtering policies (reduces exposure but impairs general browsing), or switching affected Linux users temporarily to a non-Chromium browser until patching is complete (eliminates exposure but creates workflow disruption). Blocking outbound HTTP/HTTPS broadly is not a practical compensating control for most environments. No workaround specific to this Input component flaw has been published by Google. Chromium-based browsers on Linux derived from affected Chromium versions should be patched through their own upstream release channels.
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