# CVE-2020-37214: Voyager 1.3.0 - Directory Traversal

> Attackers can read arbitrary system files via path manipulation in the Voyager admin asset endpoint, exposing sensitive configuration data.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-w79v-5572-69vq

## What is CVE-2020-37214?

CVE-2020-37214 is a high-severity path traversal vulnerability in The Control Group Voyager, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Voyager 1.3.0 contains a directory traversal vulnerability that allows attackers to access sensitive system files by manipulating the asset path parameter. Attackers can exploit the path parameter in /admin/voyager-assets to read arbitrary files like /etc/passwd and .env configuration files.

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

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


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

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

## Is CVE-2020-37214 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37214 and fix it if it is affected.

What it is: CVE-2020-37214 is a high-severity path traversal vulnerability in The Control Group Voyager, published on 11 Feb 2026. 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-37214 exists.

Affected product: The Control Group Voyager. 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-37214/ (Markdown: https://insights.sbomify.com/CVE-2020-37214/index.md)
```

## Sources

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

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