CVE-2026-11309
Google Chrome ≤ 149.0.7827.53
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2026-11309 is a medium-severity Origin Validation Error (CWE-346) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Match Legitimate Resource Name or Location (T1036.005); ranked at the 3th 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-34770
Vulnerability Data
Insufficient policy enforcement in History in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
UI spoofing via crafted HTML directly enables masquerading as a legitimate resource/location in browser history.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces access policies on browser history and UI rendering, countering the insufficient policy enforcement that enabled the origin-validation UI spoofing.
Enforces information-flow rules between origins, directly mitigating the CWE-346 origin-validation flaw that allowed crafted pages to spoof Chrome history UI.
Protects session authenticity to reduce the impact of UI spoofing attacks that rely on misleading the user about page origin or history state.
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.
Authentication directly verifies the source of users/services/hardware, mitigating origin validation failures.
Verifying identity assertions enforces origin validation for conveyed claims.
Documenting authorized flows supports origin validation by defining expected sources.
Protecting networks from unauthorized access requires origin checks on communication sources.
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.
Network security controls enforce origin validation at network boundaries.
Security of network services includes validating the authenticity of service endpoints.
Network segregation reduces exposure but does not directly validate origins.
Application security requirements explicitly call for origin validation of inputs and communications.
Secure architecture principles encourage origin checks but do not mandate them.
Secure coding practices include implementing proper origin validation to prevent spoofing.