Cyber Resilience

CVE-2026-14110

Google Chrome ≤ 150.0.7871.47

Published
30 June 2026
Modified
02 July 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.0019 9th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-14110 is a medium-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Inappropriate implementation in DarkMode in Google Chrome prior to 150.0.7871.47 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 Techniques

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1566 Phishing Initial Access
Adversaries may send phishing messages to gain access to victim systems.
T1566.002 Spearphishing Link Initial Access
Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems.
T1566.003 Spearphishing via Service Initial Access
Adversaries may send spearphishing messages via third-party services in an attempt to gain access to victim systems.
T1598 Phishing for Information Reconnaissance
Adversaries may send phishing messages to elicit sensitive information that can be used during targeting.
T1598.003 Spearphishing Link Reconnaissance
Adversaries may send spearphishing messages with a malicious link to elicit sensitive information that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-14142Same product: Google Chrome
CVE-2026-14410Same product: Google Chrome
CVE-2026-13978Same product: Google Chrome
CVE-2025-5066Same product: Google Chrome
CVE-2024-7020Same product: Google Chrome
CVE-2023-2938Same product: Google Chrome
CVE-2026-13956Same product: Google Chrome
CVE-2025-12911Same product: Google Chrome
CVE-2026-13837Same product: Google Chrome
CVE-2026-13960Same product: Google Chrome

Affected Assets

google
chrome
≤ 150.0.7871.47

Mitigating Controls

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 require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.

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.

finds

Security testing can detect missing frame protections, but does not itself implement the control.

prevents

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

degrades

Web filtering can block or sandbox untrusted frames, but does not enforce application-level frame-busting or CSP.

prevents

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

prevents

Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.

prevents

Secure architecture principles include isolation of UI layers and proper use of browser security controls.

References