EUVD-2026-34523
GHSA-8m93-jvcq-2gjv
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 V8 in Google Chrome 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 Chrome's V8 JavaScript engine (versions prior to 149.0.7827.53) exposes sensitive process memory to remote attackers who can lure a victim to a crafted HTML page. The CVSS vector (PR:N/UI:R/C:H) confirms unauthenticated remote triggering with high confidentiality impact, though exploitation requires one click of user interaction. No public exploit identified at time of analysis, and EPSS sits at the 11th percentile (0.03%), suggesting low observed exploitation pressure despite the medium-severity classification.
Technical ContextAI
V8 is Google's open-source, high-performance JavaScript and WebAssembly engine embedded in Chrome. CWE-125 (Out-of-bounds Read) describes a condition where a program reads data past the end of an allocated buffer; in V8's JIT-compiled execution environment this can expose adjacent heap or stack memory containing pointers, tokens, or other in-process secrets. The attack surface is the HTML rendering pipeline: a crafted page triggers the V8 parser or compiler to process malformed script or bytecode, causing the OOB read before any sandbox boundary fully contains the data leak. Affected CPE scope covers Google Chrome on all desktop platforms prior to version 149.0.7827.53, as confirmed by the EUVD affected-versions record (EUVD-2026-34523).
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later, which contains the vendor-released patch per the stable channel release announcement at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's auto-update mechanism will deliver this version automatically on most desktop installations; administrators managing enterprise fleets should verify deployment via policy or endpoint telemetry. If immediate patching is not feasible, the primary compensating control is to restrict or disable JavaScript execution for untrusted origins using Chrome enterprise policies (e.g., JavaScriptBlockedForUrls), though this will break functionality on many legitimate sites and should be scoped carefully. There is no workaround that eliminates the OOB read without patching; blocking JavaScript wholesale is the only configuration-level mitigation with meaningful effect.
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