EUVD-2026-40814
GHSA-pjw9-rwh3-j5j3
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Renderer compromise prerequisite elevates AC to High; network-delivered crafted page justifies AV:N; UI:R retained as victim must interact; I:L reflects UI spoofing only.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
Inappropriate implementation in Printing in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
UI spoofing in Google Chrome's Printing subsystem (all versions prior to 150.0.7871.47) can be triggered by a remote attacker who has already compromised the renderer process, enabling misrepresentation of critical browser UI via a crafted HTML page. This is a post-exploitation primitive rather than an initial-access vector - the renderer must be independently compromised before this flaw is reachable. No public exploit code exists and CISA SSVC rates exploitation as none, consistent with the low EPSS score of 0.18% (8th percentile), placing real-world urgency squarely in routine maintenance rather than emergency response.
Technical ContextAI
The vulnerability is rooted in CWE-451 (User Interface Misrepresentation of Critical Information) within Chrome's Printing implementation. Chrome employs a multi-process architecture where renderer processes handle untrusted web content inside a sandbox, while the privileged browser process governs system dialogs including print interfaces. When the renderer is already controlled by an attacker, a crafted HTML page can manipulate the Printing code path to surface spoofed UI elements - potentially deceiving users into confirming unintended actions or interacting with falsified dialogs that appear to originate from the browser or OS. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome builds on Windows, macOS, and Linux prior to the patched release.
RemediationAI
Upgrade Google Chrome to version 150.0.7871.47 or later, which contains the vendor-released patch addressing this printing spoofing flaw, as confirmed by the Chrome stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Because exploitation requires prior renderer compromise, organizations without an immediate patching window should focus compensating controls on preventing renderer escape rather than the printing vulnerability itself - enforce Chrome's Site Isolation and sandbox policies, use enterprise policy to disable or restrict printing if not operationally required (note: this may disrupt legitimate workflows), and deploy proxy-based filtering to block access to known malicious web content that could serve as renderer exploit delivery. These controls reduce the likelihood of reaching the prerequisite condition rather than mitigating the printing flaw directly.
Same 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