CVE-2025-20125 in the critical feed json
Cisco Identity Services Engine Insufficient Authorization Bypass Vulnerability
published 2025-02-05 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-2153
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.5%
- EPSS 16.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
A vulnerability in an API of Cisco ISE could allow an authenticated, remote attacker with valid read-only credentials to obtain sensitive information, change node configurations, and restart the node.
This vulnerability is due to a lack of authorization in a specific API and improper validation of user-supplied data. An attacker could exploit this vulnerability by sending a crafted HTTP request to a specific API on the device. A successful exploit could allow the attacker to attacker to obtain information, modify system configuration, and reload the device. Note: To successfully exploit this vulnerability, the attacker must have valid read-only administrative credentials. In a single-node deployment, new devices will not be able to authenticate during the reload time.
Patch / fix
- cisco identity_services_engine 3.1
Timeline
- Published
- First public exploit (EDB-52397)
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
16.49% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-52397 Cisco ISE 3.0 - Authorization Bypass remote, 2025-08-11
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Cisco Cisco Identity Services Engine Software
- Cisco Cisco ISE Passive Identity Connector
Classification
References
Sources
- CVE List CVE-2025-20125
- NVD CVE-2025-20125
Fencer Vulns 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.