# CVE-2020-26073: Cisco SD-WAN vManage Directory Traversal Vulnerability

> Unauthenticated attackers can exploit directory traversal in Cisco SD-WAN vManage APIs to access sensitive information like credentials and tokens.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/RL:X/RC:X/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-593h-gxfm-rj8p

## What is CVE-2020-26073?

CVE-2020-26073 is a high-severity path traversal vulnerability in Cisco Catalyst Sd-Wan Manager, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the application data endpoints of Cisco SD-WAN vManage Software could allow an unauthenticated, remote attacker to gain access to sensitive information.
The vulnerability is due to improper validation of directory traversal character sequences within requests to application programmatic interfaces (APIs). An attacker could exploit this vulnerability by sending malicious requests to an API within the affected application. A successful exploit could allow the attacker to conduct directory traversal attacks and gain access to sensitive information including credentials or user tokens.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

Weakness: CWE-35 (Path Traversal: '.../...//')

## Which versions are affected by CVE-2020-26073?

It affects 1 product.


Products: Cisco Catalyst Sd-Wan Manager.

## How do I fix CVE-2020-26073?

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

## Is CVE-2020-26073 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-26073 exists.

Public exploit code:

- Cisco SD-WAN vManage Software - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-26073.yaml

## 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-2020-26073 and fix it if it is affected.

What it is: CVE-2020-26073 is a high-severity path traversal vulnerability in Cisco Catalyst Sd-Wan Manager, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-26073 exists.

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-2020-26073/ (Markdown: https://insights.sbomify.com/CVE-2020-26073/index.md)
```

## Sources

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

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