CVE-2025-2197 json
Type Confusion Vulnerability in Browser
published last yr. modified 4mo ago also EUVD-2025-11510
- cvss
- 4.3
- 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 22%
- public exploits
- 0
- none known
Summary
Browser is affected by type confusion vulnerability, successful exploitation of this vulnerability may affect service availability.
Patch / fix
- Honor com. hihonor.baidu.browser 8.1.1.3
Is CVE-2025-2197 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.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
Affected products
- Honor com. hihonor.baidu.browser
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
honor.com
/global/security/cve-2025-2197/
vendor-advisory
Sources
- CVE List CVE-2025-2197
- NVD CVE-2025-2197
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.