CVE-2025-20270VulnerabilityPublished 3 Sep 2025Updated 5 Sep 2025

CVE-2025-20270: Cisco Evolved Programmable Network Manager (EPNM) · Information Exposure

Affects Cisco Evolved Programmable Network Manager (EPNM)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Cisco Cisco Evolved Programmable Network Manager (EPNM)	Affected =7.0.0 =7.1.1 =7.1.2.1 =7.0.1.3 =7.1.3 =7.1.2 =7.0.1.2 =7.0.1.1 =7.0.1 =7.1.0	Fixed in–

AI-suggested

Beyond standard best practices such as applying patches when available, European organizations should implement strict access controls and monitoring on Cisco EPNM instances. Specifically, they should: 1) Restrict low-privileged user accounts to the minimum necessary scope and regularly audit these accounts for unusual activity. 2) Employ network segmentation and firewall rules to limit access to the EPNM management interface only to trusted administrative networks and personnel. 3) Enable detailed logging and alerting on API access to detect anomalous requests that could indicate exploitation attempts. 4) Use multi-factor authentication (MFA) for all users accessing the management interface to reduce the risk of credential compromise. 5) Conduct regular vulnerability assessments and penetration tests focusing on management interfaces to identify potential abuse of API endpoints. 6) If possible, deploy Cisco EPNM in isolated environments or virtual private networks to reduce exposure to external threats. 7) Stay informed on Cisco advisories for patches or workarounds addressing this vulnerability and apply them promptly once released.

Description

A vulnerability in the web-based management interface of Cisco Evolved Programmable Network Manager (EPNM) and Cisco Prime Infrastructure could allow an authenticated, remote attacker to obtain sensitive information from an affected system. This vulnerability is due to improper validation of requests to API endpoints. An attacker could exploit this vulnerability by sending a valid request to a specific API endpoint within the affected system. A successful exploit could allow a low-privileged user to view sensitive configuration information on the affected system that should be restricted. To exploit this vulnerability, an attacker must have access as a low-privileged user.  

Impact

For European organizations, the exposure of sensitive network configuration information could have significant operational and security implications. Cisco EPNM is widely used in large enterprise and service provider networks to manage network devices and configurations. Unauthorized access to configuration details could enable attackers to map network topologies, identify critical assets, and plan more sophisticated attacks such as lateral movement or targeted intrusions. While the vulnerability does not allow direct system compromise or denial of service, the confidentiality breach could undermine trust in network management systems and potentially lead to regulatory compliance issues under GDPR if sensitive personal or operational data is exposed. Organizations relying on Cisco EPNM for network orchestration and monitoring should consider this vulnerability a risk to their network security posture, especially if low-privileged user accounts are shared or weakly controlled.

References

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-epnm-info-dis-zhPPMfgz (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Sep 2025, 20:22 UTC

Technical details

References

Community reviews

Related threats