Cyber Resilience

CVE-2026-0904

Google Chrome ≤ 144.0.7559.59

Published
20 January 2026
Modified
29 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS Score 0.0017 6th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-0904 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 Spearphishing Link (T1566.002); ranked at the 6th 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 CM-7 (Least Functionality) — 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

Incorrect security UI in Digital Credentials in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform domain spoofing via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)
CWE-451

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1566.002 Spearphishing Link Initial Access
Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems.
attack.mitre.org →
Why these techniques?

Incorrect security UI enables domain spoofing via crafted HTML, directly facilitating spearphishing links to deceive users.

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

CVEs Like This One

CVE-2026-7935Same product: Apple Macos
CVE-2026-0906Same product: Apple Macos
CVE-2026-8561Same product: Apple Macos
CVE-2026-5895Same product: Apple Macos
CVE-2026-11227Same product: Apple Macos
CVE-2026-3927Same product: Apple Macos
CVE-2026-2316Same product: Apple Macos
CVE-2026-11300Same product: Apple Macos
CVE-2026-11294Same product: Apple Macos
CVE-2026-3937Same product: Apple Macos

Affected Assets

google
chrome
≤ 144.0.7559.59 · ≤ 144.0.7559.60

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
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

SI-2 Flaw Remediation good match
prevent

Directly requires timely patching of the Chrome flaw that produces the incorrect Digital Credentials UI allowing domain spoofing.

CM-7 Least Functionality partial match
prevent

Least-functionality settings can disable or restrict the vulnerable Digital Credentials feature until the UI defect is remediated.

SC-18 Mobile Code partial match
prevent

Mobile-code restrictions limit execution of crafted HTML pages that trigger the spoofing condition in the browser UI.

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