EUVD-2026-33127
GHSA-7qvp-f7h8-6j9j
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Media in Google Chrome on ChromeOS prior to 148.0.7778.216 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: High)
AnalysisAI
Memory disclosure in Google Chrome's Media component on ChromeOS allows a remote attacker who has already compromised the renderer process to read potentially sensitive data from process memory via a specially crafted HTML page. Affected versions are all Chrome builds prior to 148.0.7778.216 on ChromeOS. This vulnerability is a chaining primitive - it cannot be exploited standalone and requires a prior renderer compromise, placing it in the context of multi-stage attack chains rather than direct exploitation. No public exploit code exists and no active exploitation has been identified at time of analysis.
Technical ContextAI
The vulnerability resides in the Media subsystem of Chromium on ChromeOS (CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*). CWE-20 (Improper Input Validation) indicates that the Media component fails to adequately validate or sanitize untrusted data originating from a renderer process before operating on it, permitting out-of-bounds or unintended memory reads. The Chromium renderer process runs in a sandboxed environment; this flaw is relevant only after that sandbox boundary has been separately breached, making it a post-exploitation information leakage primitive rather than an initial access vector. ChromeOS-specific media handling paths appear to introduce the inadequate validation not present on other platforms.
RemediationAI
Update Google Chrome on ChromeOS to version 148.0.7778.216 or later, as confirmed by the vendor's Stable Channel advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html. ChromeOS devices with auto-update enabled should receive this patch automatically; administrators managing enterprise fleets should verify deployment via the Google Admin console. As a compensating control, organizations can enforce Chrome update policies to block use of unpatched versions. Because exploitation requires a pre-existing renderer compromise, mitigating initial renderer exploitation vectors (e.g., disabling JavaScript from untrusted origins via Site Isolation policy, or restricting access to untrusted web content) reduces the likelihood of the prerequisite condition being met, though these controls have usability trade-offs in general-purpose browsing contexts.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today