CVE-2025-9867 json
Inappropriate implementation in Downloads in Google Chrome on Android prior to 140.0.7339.80 allowed a remote attacker to perform UI spoofi…
published last yr. modified 4mo ago also EUVD-2025-28893
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Inappropriate implementation in Downloads in Google Chrome on Android prior to 140.0.7339.80 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
Patch / fix
- google chrome 140.0.7339.80
- chromium Debian 12 140.0.7339.80-1~deb12u1
- chromium Debian 13 140.0.7339.80-1~deb13u1
- chromium Debian 14 140.0.7339.80-1
debian advisories DEBIAN-CVE-2025-9867
- chromium openSUSE Tumbleweed 140.0.7339.80-1.1
opensuse advisories openSUSE-SU-2025:15524-1
Is CVE-2025-9867 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.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-451 User Interface (UI) Misrepresentation of Critical Information
- Technology feeds
References
-
chromereleases.googleblog.com
/2025/09/stable-channel-update-for-desktop.html
release-notes
-
issues.chromium.org
/issues/415496161
issue-tracking, permissions-required
Sources
- CVE List CVE-2025-9867
- NVD CVE-2025-9867
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.