Cyber Resilience

CVE-2026-9110

Google Chrome ≤ 148.0.7778.179

Published
20 May 2026
Modified
23 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L
EPSS Score 0.0034 26th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

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

Operationally, ranked at the 26th 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 SC-3 (Security Function Isolation) and SC-39 (Process Isolation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Inappropriate implementation in UI in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Critical)

CWE(s)
CWE-451

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

Insufficient information to map techniques.
Confidence: LOW · MITRE ATT&CK Enterprise v19.0

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1185 Browser Session Hijacking Collectionconfidence: HIGH
UI spoofing in the browser enables browser session hijacking by deceiving the user into interacting with a fake interface.
attack.mitre.org →
T1566.002 Spearphishing Link Initial Accessconfidence: MEDIUM
UI spoofing can be used to trick users into clicking malicious links that lead to credential theft or further exploitation.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

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

Affected Assets

google
chrome
≤ 148.0.7778.179

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-39 Process Isolation
  • SC-3 Security Function Isolation
  • SI-16 Memory Protection
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-39 Process Isolation good match
prevent

Directly enforces process isolation between the compromised renderer and the browser UI process, blocking the renderer from performing UI spoofing.

SC-3 Security Function Isolation good match
prevent

Requires isolation of security functions (browser UI) from untrusted code (renderer), directly mitigating the inappropriate UI implementation flaw.

SI-16 Memory Protection partial match
prevent

Applies memory protection mechanisms that reduce the likelihood of successful renderer compromise needed to trigger the UI spoofing.

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.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect UI misrepresentation vulnerabilities before deployment.

A.6.3 Information security awareness, education and training partial match
prevents

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

A.8.23 Web filtering partial match
mitigates

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

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
prevents

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

A.8.28 Secure coding partial match
prevents

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

References