Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L
Network delivery requires no privileges, but high complexity and mandatory UI gestures limit exploitability; UI spoofing yields only limited integrity impact with no confidentiality loss.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Autofill in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
UI spoofing via Chrome's Autofill component affects all desktop installations prior to version 150.0.7871.47, enabling a remote attacker to misrepresent interface elements through a crafted HTML page. Exploitation requires both navigating to an attacker-controlled page and performing specific UI gestures, reflected in CVSS AC:H and UI:R - passive browsing is insufficient. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the CVSS 4.2 Medium score reflects limited integrity and availability impact with no confidentiality loss.
Technical ContextAI
The vulnerability resides in Chrome's Autofill subsystem, which parses and renders HTML form elements to surface saved credential or data suggestions. CWE-451 (User Interface Misrepresentation of Critical Information) identifies the root cause as a failure to appropriately constrain how crafted HTML can influence the Autofill UI rendering pipeline - allowing attacker-supplied markup to alter or spoof the visual representation of interface elements. Because Autofill operates at the browser UI layer rather than within a sandboxed renderer context, such misrepresentation can appear authoritative to the user. Affected versions are all Chrome desktop stable channel builds below 150.0.7871.47, as confirmed by both the Chrome Releases advisory and EUVD-2026-40581.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later using Chrome's built-in update mechanism (Settings > Help > About Google Chrome) or via enterprise deployment tooling. The vendor-released patch is documented at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. As a compensating control prior to patching, disabling Autofill entirely (Settings > Autofill and passwords > disable saved passwords and payment methods) removes the affected attack surface at the cost of user convenience. Restricting navigation to untrusted external sites via browser policy (e.g., enterprise URL allowlisting) reduces exposure but does not eliminate risk from compromised trusted sites. No additional vendor-documented workarounds are available in the referenced advisories.
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-40581
GHSA-qhpw-xfcg-74cw