CVE-2025-12447 json
Incorrect security UI in Omnibox in Google Chrome on Android prior to 142.0.7444.59 allowed a remote attacker who convinced a user to engag…
published last yr. modified last mo. also EUVD-2025-50789
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Incorrect security UI in Omnibox in Google Chrome on Android prior to 142.0.7444.59 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
Patch / fix
- google chrome 142.0.7444.59
- chromium Debian 12 142.0.7444.59-1~deb12u1
- chromium Debian 13 142.0.7444.59-1~deb13u1
- chromium Debian 14 142.0.7444.59-1
debian advisories DEBIAN-CVE-2025-12447
- chromium openSUSE Leap 16.0 142.0.7444.162-bp160.1.1
- chromium openSUSE Tumbleweed 142.0.7444.59-2.1
opensuse advisories openSUSE-SU-2025:20076-1openSUSE-SU-2025:15687-1
Is CVE-2025-12447 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
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L |
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
- Technology feeds
References
-
chromereleases.googleblog.com
/2025/10/stable-channel-update-for-desktop_28.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/442636157
issue-tracking, permissions-required
Sources
- CVE List CVE-2025-12447
- NVD CVE-2025-12447
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.