CVE-2026-8006
Google Chrome ≤ 148.0.7778.96
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:LSummary
CVE-2026-8006 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Masquerading (T1036); ranked at the 2th 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 CM-11 (User-installed Software) and SC-18 (Mobile Code) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-28115
Vulnerability Data
Insufficient policy enforcement in DevTools in Google Chrome prior to 148.0.7778.96 allowed an attacker who convinced a user to install a malicious extension to perform UI spoofing via a crafted Chrome Extension. (Chromium security severity: Low)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability enables UI spoofing via malicious browser extension, directly facilitating masquerading and browser extension abuse.
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly restricts user installation of untrusted extensions that could be abused for UI spoofing.
Requires control and verification of mobile code (extensions) before execution to block crafted malicious payloads.
Enforces security policies on extension capabilities, mitigating the insufficient DevTools policy enforcement described in the CVE.
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.