CVE-2026-0906: Google Chrome · Incorrect Security UI
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 144.0.7559.59 as a priority.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 144.0.7559.59
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Google Chrome to 144.0.7559.59.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
European organizations should implement a multi-layered mitigation strategy beyond simply updating Chrome. First and foremost, ensure all Android devices are updated to Chrome version 144.0.7559.59 or later through managed device policies or user education. Deploy Mobile Device Management (MDM) solutions to enforce browser updates and restrict installation of unapproved apps. Conduct targeted user awareness training emphasizing the risks of URL spoofing and instruct users to verify website authenticity through additional means such as bookmarks or direct navigation rather than relying solely on the URL bar. Implement advanced email and web filtering solutions to detect and block phishing attempts that exploit this vulnerability. Encourage the use of multi-factor authentication (MFA) to reduce the impact of credential theft. Monitor network traffic for unusual access patterns that may indicate successful phishing exploitation. Finally, maintain an incident response plan that includes procedures for handling phishing incidents and compromised credentials. Organizations should also track updates from Google and apply patches promptly as part of their vulnerability management program.
Description
Incorrect security UI in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: Low)