CVE-2026-11227
Google Chrome ≤ 149.0.7827.53
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NSummary
CVE-2026-11227 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Spearphishing Link (T1566.002); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-34688
Vulnerability Data
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)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Domain spoofing in browser UI directly facilitates spearphishing links by deceiving users about site legitimacy.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires patching the Chrome browser to remediate the incorrect Tab Hover Card UI that permits domain spoofing via crafted names.
Enforces validation of domain-name inputs before they are rendered in security UI surfaces, blocking the crafted-name spoofing vector.
Filters or sanitizes domain information presented to users, mitigating UI misrepresentation of the true origin.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly address design and implementation of accurate, non-spoofable UI elements.
User awareness training helps people recognize and avoid harm from UI misrepresentation such as phishing, but does not prevent the flaw itself.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect UI misrepresentation vulnerabilities before deployment.
Security awareness training can teach users to recognize UI misrepresentation and phishing attempts.
Web filtering can block known phishing sites that exploit UI misrepresentation.
Secure development lifecycle includes UI/UX security requirements that can prevent misrepresentation of critical information.
Application security requirements can mandate proper display and validation of critical information in the UI.
Secure coding practices can prevent UI flaws that obscure or spoof critical information.