Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
AC:H reflects mandatory renderer pre-compromise; C:H for arbitrary process memory read; no integrity or availability impact applies.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Uninitialized Use in Media in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Uninitialized memory exposure in Google Chrome's Media component allows a remote attacker who has already compromised the renderer process to read potentially sensitive data from process memory by serving a crafted HTML page. Affected versions are all Chrome releases prior to 150.0.7871.47, across desktop platforms. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; exploitation requires a chained renderer compromise, significantly constraining real-world risk despite the high confidentiality impact rating.
Technical ContextAI
CWE-457 (Use of Uninitialized Variable) describes a class of memory-safety defect where allocated memory is read before being written, potentially exposing stale heap or stack contents from prior allocations. In Chrome's Media subsystem - which handles decoding and processing of audio and video content - an uninitialized buffer read can surface arbitrary bytes from the renderer process's address space when a specially crafted media element or HTML page is parsed. Chrome's multi-process architecture means this flaw is exercised within the renderer sandbox, so an attacker must first achieve renderer-process code execution through a separate vulnerability before this information-disclosure bug becomes reachable. The affected CPE, per EUVD data, is Chrome versions below 150.0.7871.47.
RemediationAI
Upgrade to Google Chrome version 150.0.7871.47 or later, available via Chrome's built-in auto-update mechanism or directly from the Chrome releases blog at chromereleases.googleblog.com (June 2026 Stable Channel update). Because exploitation requires a pre-compromised renderer process, organizations that cannot immediately patch should focus on ensuring no other unpatched renderer vulnerabilities are present, as those are the necessary precursor. Enabling Chrome's Enhanced Safe Browsing can reduce the likelihood of landing on attacker-controlled pages. For enterprise deployments, enforcing Chrome version policy via Google Admin Console or endpoint management tooling will ensure fleet-wide coverage. No separate workaround for the Media component itself is available without patching.
Same weakness CWE-457 – Use of Uninitialized Variable
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40658
GHSA-4fm8-wg27-q6xr