Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.41% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-20151High confidence
Cisco IOS and IOS XE Software SNMPv3 Configuration Restriction Vulnerability
Cisco · Cisco IOS XE Catalyst SD-WAN
Official source article: Cisco CISCO-SA-SNMPV3-QKEYVZSY ↗. Check the applicable product and release in the original source.
4.3MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4,085 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Cisco Cisco IOS XE Catalyst SD-WAN and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 4,085 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Cisco PSIRT: 4,085 affected or under-investigation product states without a fixed product state in the same current advisory
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
cisco-sa-snmpv3-qKEYvzsy · CSAF 2.0 · revision 1.0.0 · finalCisco PSIRTCisco IOS and IOS XE Software SNMPv3 Configuration Restriction Vulnerability
The vendor explicitly identifies these products as affected by this CVE.
- 15.1(2)T
- 12.2(46)EY
- 12.2(25)SW9
- 12.2(31)XN2
- 12.2(31)SB1a
- 12.2(50)SG3
- 12.3(14)YQ5
- 12.2(25)EWA5
- 12.2(18)SXD7b
- 12.3(4)XD4
- 12.3(11)YF2
- 12.2(2)XT2
- Summary
- Complete.
- Remediation
- Cisco has released software updates that address this vulnerability.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4,085 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
A vulnerability in the implementation of the Simple Network Management Protocol Version 3 (SNMPv3) feature of Cisco IOS Software and Cisco IOS XE Software could allow an authenticated, remote attacker to poll an affected device using SNMP, even if the device is configured to deny SNMP traffic from an unauthorized source or the SNMPv3 username is removed from the configuration. This vulnerability exists because of the way that the SNMPv3 configuration is stored in the Cisco IOS Software and Cisco IOS XE Software startup configuration. An attacker could exploit this vulnerability by polling an affected device from a source address that should have been denied. A successful exploit could allow the attacker to perform SNMP operations from a source that should be denied. Note: The attacker has no control of the SNMPv3 configuration. To exploit this vulnerability, the attacker must have valid SNMPv3 user credentials. For more information, see the section of this advisory.
What
A vulnerability in the implementation of the Simple Network Management Protocol Version 3 (SNMPv3) feature of Cisco IOS Software and Cisco IOS XE Software could allow an authenticated, remote attacker to poll an affected device using SNMP, even if the device is configured to deny SNMP traffic from an unauthorized source or the SNMPv3 username is removed from the configuration. This vulnerability exists because of the way that the SNMPv3 configuration is stored in the Cisco IOS Software and Cisco IOS XE Software startup configuration. An attacker could exploit this vulnerability by polling an affected device from a source address that should have been denied. A successful exploit could allow the attacker to perform SNMP operations from a source that should be denied. Note: The attacker has no control of the SNMPv3 configuration. To exploit this vulnerability, the attacker must have valid SNMPv3 user credentials. For more information, see the section of this advisory.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
A vulnerability in the implementation of the Simple Network Management Protocol Version 3 (SNMPv3) feature of Cisco IOS Software and Cisco IOS XE Software could allow an authenticated, remote attacker to poll an affected device using SNMP, even if the device is configured to deny SNMP traffic from an unauthorized source or the SNMPv3 username is removed from the configuration. This vulnerability exists because of the way that the SNMPv3 configuration is stored in the Cisco IOS Software and Cisco IOS XE Software startup configuration. An attacker could exploit this vulnerability by polling an affected device from a source address that should have been denied. A successful exploit could allow the attacker to perform SNMP operations from a source that should be denied. Note: The attacker has no control of the SNMPv3 configuration. To exploit this vulnerability, the attacker must have valid SNMPv3 user credentials. For more information, see the section of this advisory.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-16 ↗
CWE-16. Open the MITRE definition for the exact weakness description.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- 15.1(2)T
- 12.2(46)EY
- 12.2(25)SW9
- 12.2(31)XN2
- 12.2(31)SB1a
- 12.2(50)SG3
- 12.3(14)YQ5
- 12.2(25)EWA5
- 12.2(18)SXD7b
- 12.3(4)XD4
- 12.3(11)YF2
- 12.2(2)XT2
- 12.2(2)XH1
- 12.2(28)SB10
- 12.4(21a)JHA
- 12.4(21a)M1
- 12.4(4)T8
- 12.2(15)CZ1
- 12.2(20)S10
- 12.2(15)MC1c
- 12.4(20)T1
- 12.2(33)IRC
- 12.2(4)MB7
- 12.3(8)YG7
- 12.4(22)XR5
- 12.2(55)EY
- 12.4(15)XY4
- 12.2(25)EWA1
- 12.2(31)SB10c
- 12.2(31)SB9b
- and 4055 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 7 May 2025 · Last source change 7 May 2025, 19:46 UTC · CWE-16
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-13920
Product sourceVendor CSAF · Cisco PSIRT
Remediation sourceVendor CSAF · Cisco PSIRT
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Cisco PSIRT ↗
- Before
- 15.1(2)T; 12.2(46)EY; 12.2(25)SW9; 12.2(31)XN2; 12.2(31)SB1a; 12.2(50)SG3; 12.3(14)YQ5; 12.2(25)EWA5; 12.2(18)SXD7b; 12.3(4)XD4; 12.3(11)YF2; 12.2(2)XT2; 12.2(2)XH1; 12.2(28)SB10; 12.4(21a)JHA; 12.4(21a)M1; 12.4(4)T8; 12.2(15)CZ1; 12.2(20)S10; 12.2(15)MC1c; 12.4(20)T1; 12.2(33)IRC; 12.2(4)MB7; 12.3(8)YG7; 12.4(22)XR5; 12.2(55)EY; 12.4(15)XY4; 12.2(25)EWA1; 12.2(31)SB10c; 12.2(31)SB9b; and 4114 more
- After
- 15.1(2)T; 12.2(46)EY; 12.2(25)SW9; 12.2(31)XN2; 12.2(31)SB1a; 12.2(50)SG3; 12.3(14)YQ5; 12.2(25)EWA5; 12.2(18)SXD7b; 12.3(4)XD4; 12.3(11)YF2; 12.2(2)XT2; 12.2(2)XH1; 12.2(28)SB10; 12.4(21a)JHA; 12.4(21a)M1; 12.4(4)T8; 12.2(15)CZ1; 12.2(20)S10; 12.2(15)MC1c; 12.4(20)T1; 12.2(33)IRC; 12.2(4)MB7; 12.3(8)YG7; 12.4(22)XR5; 12.2(55)EY; 12.4(15)XY4; 12.2(25)EWA1; 12.2(31)SB10c; 12.2(31)SB9b; and 4055 more
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Cisco PSIRT ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.