Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Network delivery via crafted HTML page with required user interaction; no auth needed; integrity-only impact from UI misrepresentation with no confidentiality or availability effect.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in Paint in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
UI spoofing in Google Chrome's Paint rendering component (all versions prior to 150.0.7871.47) allows a remote unauthenticated attacker to misrepresent browser interface elements by luring a user to a crafted HTML page. The flaw stems from an inappropriate implementation in the Paint subsystem (CWE-451), enabling visual manipulation of browser UI state to deceive users into false trust decisions. No public exploit has been identified, SSVC rates exploitation as none, and EPSS sits at the 11th percentile - making this a low-urgency patch despite Chrome's near-ubiquitous deployment footprint.
Technical ContextAI
The vulnerability resides in the Paint component of the Chromium rendering engine - the subsystem responsible for compositing and drawing visual elements to the screen. CWE-451 (User Interface Misrepresentation of Critical Information) identifies the root cause as a failure to properly constrain how a crafted HTML page can influence the rendering of browser UI chrome, potentially allowing attackers to falsify security indicators, overlay misleading content, or distort address bar representation. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, spanning all Chrome platform builds prior to 150.0.7871.47. The Chromium issue tracker entry (https://issues.chromium.org/issues/513988889) likely contains deeper technical detail but may be access-restricted per Google's disclosure policy.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later immediately via the built-in browser updater at chrome://settings/help or by referencing the Chrome Stable Channel Update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. SUSE Linux administrators should apply updated chromium packages from SUSE's official repositories once a patched build is published - no separate SUSE advisory URL was provided in the available data. No documented workaround exists for this vulnerability; organizations that cannot immediately deploy the patch can reduce exposure by enforcing safe browsing controls at the proxy or DNS layer to block access to unknown external URLs, though this does not eliminate the vulnerability and imposes usability trade-offs. Chrome's auto-update mechanism typically propagates patches within 24-48 hours for consumer and managed enterprise deployments, making this a low-friction remediation in most environments.
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-40667
GHSA-7v9m-g8gq-4fmx