# CVE-2026-20262: Cisco Catalyst SD-WAN Manager Directory or Path Traversal

> Authenticated attackers can overwrite arbitrary files via the web UI, potentially leading to root privilege escalation on Cisco Catalyst SD-WAN Manager.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Yes, since 15 Jun 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-p45r-gcc9-fr7f

## What is CVE-2026-20262?

CVE-2026-20262 is a medium-severity path traversal vulnerability in Cisco Catalyst Sd-Wan Manager, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web UI of Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, could allow an authenticated, remote attacker to create a file or overwrite any file on the filesystem of an affected system.

This vulnerability exists because the affected software does not properly validate user-supplied input during a file upload process. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected API endpoint of the affected system. A successful exploit could allow the attacker to create or overwrite any file on the underlying operating system. This file could later be used to elevate to root. To exploit this vulnerability, the attacker must have valid credentials with at least a lower-privileged, single-task user account.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-20262?

It affects 1 product.


Products: Cisco Catalyst Sd-Wan Manager.

## How do I fix CVE-2026-20262?

No fix has been published for CVE-2026-20262 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Jun 2026.

## Is CVE-2026-20262 being exploited?

Yes. Attackers have exploited CVE-2026-20262 in the wild since at least 15 Jun 2026.

Public exploit code:

- PoC de CVE-2026-20262: escritura arbitraria de archivos por path traversal en Cisco Catalyst SD-WAN Manager (autenticado). (github_poc): https://github.com/fevar54/CVE-2026-20262-Cisco-Catalyst-SD-WAN-Manager-Arbitrary-File-Write-
- CVE-2026-20262 - Draft (github_poc): https://github.com/HORKimhab/CVE-2026-20262

## Other vulnerabilities in Cisco Catalyst Sd-Wan Manager

- [CVE-2026-20182](https://insights.sbomify.com/CVE-2026-20182/): Cisco Catalyst SD-WAN Controller Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2026-20127](https://insights.sbomify.com/CVE-2026-20127/): Cisco Catalyst SD-WAN Controller and Manager Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2026-76504](https://insights.sbomify.com/CVE-2026-76504/): Cisco Catalyst SD-WAN Manager Hex Encoding (critical 9.8, exploited in the wild)
- [CVE-2026-20245](https://insights.sbomify.com/CVE-2026-20245/): Cisco Catalyst SD-WAN Manager Improper Encoding or Escaping of Output (high 7.8, exploited in the wild)
- [CVE-2022-20775](https://insights.sbomify.com/CVE-2022-20775/): Cisco SD-WAN Path Traversal (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20262 and fix it if it is affected.

What it is: CVE-2026-20262 is a medium-severity path traversal vulnerability in Cisco Catalyst Sd-Wan Manager, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-20262 in the wild since at least 15 Jun 2026.

Affected product: Cisco Catalyst Sd-Wan Manager. 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-2026-20262/ (Markdown: https://insights.sbomify.com/CVE-2026-20262/index.md)
```

## Sources

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

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