CVE-2026-0907: 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, 11:07 UTC
- EPSS
- 8.8% chance of exploitation in 30 days – higher than 95% 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
To mitigate CVE-2026-0907, European organizations should implement the following specific measures: 1) Ensure all Chrome browsers are updated to version 144.0.7559.59 or later to apply the security fix. 2) Deploy enterprise policies that enforce automatic browser updates and restrict use of outdated versions. 3) Conduct targeted user awareness training focusing on recognizing phishing attempts and suspicious UI elements, especially in multi-window or split view scenarios. 4) Utilize web filtering and URL reputation services to block access to known malicious sites that could exploit UI spoofing. 5) Monitor network traffic and endpoint logs for unusual web activity or repeated access to suspicious HTML content. 6) Encourage the use of multi-factor authentication to reduce the impact of credential theft resulting from phishing. 7) Collaborate with IT and security teams to test and validate browser configurations and extensions that may affect UI rendering. These steps go beyond generic advice by emphasizing organizational controls, user education, and proactive monitoring tailored to this vulnerability's characteristics.
Description
Incorrect security UI in Split View in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)