CVE-2026-0906 in the critical feed json
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 (UR…
published 9mo ago modified 4mo ago also EUVD-2026-3455
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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)
Patch / fix
- google chrome 144.0.7559.59
- chromium Debian 12 144.0.7559.59-1~deb12u1
- chromium Debian 13 144.0.7559.59-1~deb13u1
- chromium Debian 14 144.0.7559.59-1
debian advisories DEBIAN-CVE-2026-0906
- chromium openSUSE Leap 16.0 144.0.7559.132-bp160.1.1
- chromium openSUSE Tumbleweed 144.0.7559.59-1.1
opensuse advisories openSUSE-SU-2026:20183-1openSUSE-SU-2026:10057-1
Is CVE-2026-0906 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 9mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-451 User Interface (UI) Misrepresentation of Critical Information
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/01/stable-channel-update-for-desktop_13.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/467448811
issue-tracking, permissions-required
Sources
- CVE List CVE-2026-0906
- NVD CVE-2026-0906
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.