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
Use after free in Codecs 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
Memory information disclosure in Google Chrome's Codecs component affects all desktop versions prior to 149.0.7827.53, enabling remote unauthenticated attackers to read potentially sensitive data from browser process memory when a user visits a specially crafted HTML page. The root cause is a use-after-free (CWE-416) in the media codec subsystem, yielding high confidentiality impact with no integrity or availability consequences per CVSS. EPSS is very low at 0.03% (11th percentile) and SSVC confirms no active exploitation, placing this firmly in the routine patch category despite its Medium severity score.
Technical ContextAI
Use-after-free (CWE-416) is a memory safety vulnerability where a program continues to use a pointer after the memory it references has been freed. In Chrome's Codecs component - responsible for audio and video decoding - the freed memory region may still contain residual sensitive data (e.g., decoded media buffers, or adjacent heap objects holding credentials or tokens) that attacker-controlled HTML can cause the browser to read and potentially expose. The CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms this is reachable from the network via crafted web content with no special privileges, but requires a user to load the page. All Google Chrome desktop releases (Windows, macOS, Linux) below version 149.0.7827.53 are affected, as indicated by the EUVD affected range and vendor stable-channel release notes.
RemediationAI
The primary fix is upgrading Google Chrome to version 149.0.7827.53 or later, confirmed by the vendor stable-channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's built-in auto-update mechanism will deliver this patch automatically; administrators should verify that auto-update is not disabled via enterprise policy and prompt users to restart the browser to finalize installation. For environments where immediate patching is not feasible, a practical compensating control is restricting user access to untrusted external web content via a web proxy with category filtering, which limits exposure to attacker-hosted crafted pages - though this carries significant usability trade-offs in general-purpose environments. No feature-level workaround to disable the affected Codecs code path is documented by Google.
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34669
GHSA-7fg2-p8pj-m24q