Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Network-delivered PDF requires no attacker privileges; victim must open it (UI:R); impact is integrity-only spoofing with no confidentiality or availability effect.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in PDFium in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to perform UI spoofing via a crafted PDF file. (Chromium security severity: Medium)
AnalysisAI
UI spoofing via a crafted PDF file in Google Chrome's PDFium rendering engine allows a remote, unauthenticated attacker to visually mislead users into performing unintended actions or trusting falsified content. All Chrome versions prior to 150.0.7871.46 are affected. Exploitation requires the victim to open a malicious PDF - no special configuration is needed beyond default Chrome behavior. No public exploit identified at time of analysis, and CISA SSVC rates exploitation as none with partial technical impact.
Technical ContextAI
PDFium is the open-source PDF rendering library embedded in Google Chrome (and Chromium-derived browsers), responsible for parsing and displaying PDF files natively within the browser. The vulnerability is classified as CWE-451 (User Interface Misrepresentation of Critical Information), a root cause where the UI layer fails to accurately represent security-critical state to the user. An 'inappropriate implementation' in PDFium allows a specially crafted PDF to manipulate how Chrome renders or presents UI elements - such as security indicators, origin information, or dialog prompts - leading to spoofing. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome desktop variants prior to 150.0.7871.46 across platforms.
RemediationAI
The primary fix is upgrading Google Chrome to version 150.0.7871.46 or later, which is confirmed as the patched stable channel release per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome typically auto-updates, but administrators managing enterprise deployments should verify update propagation via policy. As a compensating control while patching is pending, organizations can restrict or disable in-browser PDF rendering by configuring Chrome to download PDFs rather than open them inline (via the 'Download PDF files instead of automatically opening them in Chrome' setting in chrome://settings/content/pdfDocuments), which prevents PDFium from processing untrusted PDF files - this carries the trade-off of reduced user convenience and shifts risk to whatever external PDF viewer is used. Blocking untrusted PDF delivery at the email gateway or proxy layer is an additional network-level control.
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
EUVD-2026-41157
GHSA-68q2-f79g-5v77