# CVE-2025-20151: Cisco IOS and IOS XE Software SNMPv3 Configuration Restriction Vulnerability

> Authenticated attackers can bypass SNMP access restrictions to poll devices from unauthorized sources, potentially reading configuration data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2025
- **Updated:** 7 May 2025
- **Also known as:** GHSA-v3x4-26xj-qrvg

## What is CVE-2025-20151?

CVE-2025-20151 is a medium-severity vulnerability in Cisco IOS XE Catalyst SD-WAN, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-16

## Which versions are affected by CVE-2025-20151?

It affects 1 product.


Products: Cisco Ios Xe Sd-Wan.

## How do I fix CVE-2025-20151?

No fix has been published for CVE-2025-20151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20151 being exploited?

There is no known exploitation of CVE-2025-20151 in the wild and no public exploit code.

## Other vulnerabilities in Cisco IOS XE Catalyst SD-WAN

- [CVE-2021-34727](https://insights.sbomify.com/CVE-2021-34727/): Cisco IOS XE SD-WAN Software Buffer Overflow Vulnerability (critical 9.8)
- [CVE-2020-3375](https://insights.sbomify.com/CVE-2020-3375/): Cisco SD-WAN Solution Software Buffer Overflow Vulnerability (critical 9.8)
- [CVE-2021-1305](https://insights.sbomify.com/CVE-2021-1305/): Cisco SD-WAN vManage Authorization Bypass Vulnerabilities (high 8.8)
- [CVE-2023-20035](https://insights.sbomify.com/CVE-2023-20035/): Cisco IOS XE SD-WAN Software Command Injection Vulnerability (high 7.8)
- [CVE-2020-3216](https://insights.sbomify.com/CVE-2020-3216/): Cisco IOS XE SD-WAN Software Authentication Bypass Vulnerability (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20151 and fix it if it is affected.

What it is: CVE-2025-20151 is a medium-severity vulnerability in Cisco IOS XE Catalyst SD-WAN, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20151 in the wild and no public exploit code.

Affected product: Cisco IOS XE Catalyst SD-WAN. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20151/ (Markdown: https://insights.sbomify.com/CVE-2025-20151/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20151
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20151
- OSV: https://osv.dev/vulnerability/CVE-2025-20151

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20151/
Summaries are generated and may contain mistakes; the official description above is the record.