Cyber Resilience

CVE-2026-5906

Google Chrome ≤ 147.0.7727.55

Published
08 April 2026
Modified
24 July 2026
Patch / advisory
View 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.0016 6th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-5906 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 Drive-by Compromise (T1189); 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-6 (Configuration Settings) — 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 Omnibox in Google Chrome on Android prior to 147.0.7727.55 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: Low)

CWE(s)
CWE-451

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
attack.mitre.org →
Why these techniques?

Vulnerability allows URL bar spoofing via crafted HTML page, directly enabling drive-by compromise when user visits malicious site.

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

CVEs Like This One

CVE-2026-14144Same product: Apple Macos
CVE-2026-2318Same product: Apple Macos
CVE-2026-2322Same product: Apple Macos
CVE-2026-2316Same product: Apple Macos
CVE-2026-5898Same product: Apple Macos
CVE-2026-11254Same product: Apple Macos
CVE-2026-0907Same product: Apple Macos
CVE-2026-0901Same product: Apple Macos
CVE-2026-8008Same product: Apple Macos
CVE-2026-0904Same product: Apple Macos

Affected Assets

google
chrome
≤ 147.0.7727.55

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • CM-6 Configuration Settings
  • SC-18 Mobile Code
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 Chrome to the fixed version that corrects the Omnibox UI rendering flaw.

CM-6 Configuration Settings partial match
prevent

Enforces secure baseline browser configuration settings that can limit exposure to crafted HTML pages abusing UI elements.

SC-18 Mobile Code partial match
prevent

Restricts or monitors mobile code (e.g., scripts in web pages) that could be used to trigger the Omnibox spoofing condition.

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