Cisco Evolved Programmable Network Manager Improper Authorization Vulnerability
🔗 CVE IDs covered (1)
📋 Description
A vulnerability in the web-based management interface of Cisco Evolved Programmable Network Manager (EPNM) could allow an authenticated, remote attacker with low privileges to access sensitive information that they are not authorized to access.
This vulnerability is due to improper authorization checks on a REST API endpoint of an affected device. An attacker could exploit this vulnerability by querying the affected endpoint. A successful exploit could allow the attacker to view session information of active Cisco EPNM users, including users with administrative privileges, which could result in the affected device being compromised.
Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
CVE-2026-20155 — Cisco Evolved Programmable Network Manager Improper Authorization Vulnerability (CVSS 3.1 8.0, CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H)
🎯 Affected products15
- Cisco Evolved Programmable Network Manager (EPNM)
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.0
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.1
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.2
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.2.1
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.3
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.3.1
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.4
- Cisco Evolved Programmable Network Manager (EPNM) 7.1.4.1
- Cisco Evolved Programmable Network Manager (EPNM) 8.0.0
- Cisco Evolved Programmable Network Manager (EPNM) 8.0.0.1
- Cisco Evolved Programmable Network Manager (EPNM) 8.0.1
- Cisco Evolved Programmable Network Manager (EPNM) 8.0.1.1
- Cisco Evolved Programmable Network Manager (EPNM) 8.1.0
- Cisco Evolved Programmable Network Manager (EPNM) 8.1.1
✅ Remediation
Cisco has released software updates that address this vulnerability. https://software.cisco.com Workarounds: There are no workarounds that address this vulnerability.