Cyber Resilience

CVE-2026-11107

Google Chrome ≤ 149.0.7827.53

Published
04 June 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-11107 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Masquerading (T1036); ranked at the 14th 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-3 (Malicious Code Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Inappropriate implementation in Downloads 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: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
Why these techniques?

UI spoofing in browser Downloads directly supports masquerading download prompts/UI and tricking users into executing malicious files.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-8008Same product: Apple Macos
CVE-2026-8006Same product: Apple Macos
CVE-2026-5897Same product: Apple Macos
CVE-2026-0901Same product: Apple Macos
CVE-2026-14144Same product: Apple Macos
CVE-2026-0904Same product: Apple Macos
CVE-2026-5906Same product: Apple Macos
CVE-2026-5882Same product: Apple Macos
CVE-2026-7935Same product: Apple Macos
CVE-2025-13107Same product: Apple Macos

Affected Assets

google
chrome
≤ 149.0.7827.53

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SI-3 Malicious Code Protection
Detect
Catch it (NIST detect / respond)
  • SI-3 Malicious Code Protection
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly addresses the root cause by requiring prompt patching of Chrome to correct the inappropriate Downloads UI implementation.

preventdetect

Malicious-code protection on downloaded files can block or alert on payloads delivered via the spoofed download UI.

detect

Continuous monitoring of browser download events and UI anomalies can identify exploitation attempts against this Chrome flaw.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly address design and implementation of accurate, non-spoofable UI elements.

PR.AT-01 partial match
prevents

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.

detects

Security testing can detect UI misrepresentation vulnerabilities before deployment.

prevents

Security awareness training can teach users to recognize UI misrepresentation and phishing attempts.

mitigates

Web filtering can block known phishing sites that exploit UI misrepresentation.

prevents

Secure development lifecycle includes UI/UX security requirements that can prevent misrepresentation of critical information.

prevents

Application security requirements can mandate proper display and validation of critical information in the UI.

prevents

Secure coding practices can prevent UI flaws that obscure or spoof critical information.

References