Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Incorrect security UI in Tab Hover Cards in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to perform domain spoofing via a crafted domain name. (Chromium security severity: Low)
AnalysisAI
Tab Hover Cards in Google Chrome prior to 149.0.7827.53 render domain names incorrectly, enabling a remote unauthenticated attacker to spoof displayed domain identity via a crafted domain name, misleading users about the true destination of a browser tab. CVSS rates Integrity impact as High (I:H), reflecting the real deception potential in phishing scenarios, while Chromium itself labels this Low severity - a notable contrast worth flagging. No public exploit identified at time of analysis, and EPSS at 0.03% (11th percentile) reflects minimal current exploitation interest.
Technical ContextAI
CWE-451 (User Interface Misrepresentation of Critical Information) describes flaws where security-critical UI elements display misleading or incorrect information, undermining user trust decisions. Tab Hover Cards are tooltip-style overlays shown in Chrome when a user hovers over a browser tab, intended to convey the page title and URL of the underlying tab. The root cause here is incorrect rendering logic within that hover card component - likely failing to normalize or validate internationalized domain names (IDN), Unicode homograph characters, or other crafted domain string formats before display, causing the card to present a spoofed domain rather than the true resolved destination. The address bar rendering pipeline (a separate code path) is not implicated. Chromium issue 448421954 is referenced but access may be restricted pending stable release.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later, as confirmed by the vendor's stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome typically self-updates, but users should verify their version via chrome://settings/help and force an update if needed. Enterprise administrators using Chrome Browser Cloud Management or Group Policy should enforce a minimum version floor of 149.0.7827.53. As a compensating control where immediate patching is not feasible, organizations should instruct users never to rely on Tab Hover Cards as a URL verification mechanism and instead confirm destinations via the address bar - noting this is a behavioral mitigation with no enforcement mechanism. Disabling Tab Hover Cards via chrome://flags/#tab-hover-cards eliminates the vulnerable UI surface but removes tab preview functionality entirely, which may impact usability for power users managing many tabs.
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-34688
GHSA-2jrr-2q54-q6ww