Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Incorrect security UI in File Input in Google Chrome prior to 149.0.7827.53 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: Low)
AnalysisAI
UI spoofing in Google Chrome's File Input component (versions prior to 149.0.7827.53) enables remote attackers to misrepresent security-critical interface elements to users through specially crafted HTML pages. The attacker must convince a target to perform specific UI gestures - such as drag-and-drop or deliberate click sequences - to trigger incorrect rendering of the browser's file selection security UI. No public exploit identified at time of analysis; EPSS at 0.03% (11th percentile) signals very low exploitation probability, consistent with no CISA KEV listing.
Technical ContextAI
The vulnerability resides in the File Input component (<input type='file'>) of Google Chrome's rendering engine, affecting all desktop platform builds prior to version 149.0.7827.53. CWE-451 (User Interface Misrepresentation of Critical Information) is the root cause class: the browser fails to correctly render or enforce visual security indicators associated with file selection dialogs, allowing a malicious HTML page to present a deceptive UI. This class of bug typically arises when UI state is not correctly synchronized with underlying security boundaries, enabling an attacker-controlled page to influence what the user perceives as a trustworthy browser-native interface. The affected versions are confirmed via ENISA EUVD-2026-34677 and the Chromium issue tracker (issues.chromium.org/issues/474583539).
RemediationAI
The primary fix is upgrading Google Chrome to version 149.0.7827.53 or later, as documented in the stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome auto-updates by default on consumer installations; enterprise administrators should verify deployment via Google Chrome Enterprise policy or patch management tooling and push the update proactively. No workarounds or compensating controls are documented for this vulnerability. Given the requirement for user interaction and the low CVSS impact score, the primary mitigation outside patching is user awareness: instruct users not to interact with unexpected file dialog prompts on unfamiliar websites, particularly those requesting specific drag-and-drop or gesture-based interaction. This is a low-friction advisory update with no known side effects.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34677
GHSA-pmhg-cprx-7ppp