# CVE-2023-39810: Path traversal in n/a

> Attackers can exploit a directory traversal flaw in BusyBox CPIO to read or modify files outside the intended directory.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Aug 2023
- **Updated:** 9 Jul 2026
- **Also known as:** AZL-61539, AZL-61600, BELL-CVE-2023-39810, CLSA-2026-1777368104, DEBIAN-CVE-2023-39810, ECHO-ca8b-4d06-0a38, GHSA-mm53-x3wx-jgr2, OESA-2025-1855, OESA-2025-1856, OESA-2025-1857, UBUNTU-CVE-2023-39810, openSUSE-SU-2026:11256-1

## What is CVE-2023-39810?

CVE-2023-39810 is a high-severity path traversal vulnerability in n/a, published on 28 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue in the CPIO command of Busybox v1.33.2 allows attackers to execute a directory traversal.

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

## Which versions are affected by CVE-2023-39810?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `busybox` | openSUSE:Tumbleweed | All versions | 1.38.0-1.1 |

Products: Busybox Busybox.

## How do I fix CVE-2023-39810?

Upgrade to a fixed version.

## Is CVE-2023-39810 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-48174](https://insights.sbomify.com/CVE-2022-48174/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-42377](https://insights.sbomify.com/CVE-2021-42377/): Memory corruption in busybox (critical 9.8)
- [CVE-2016-2148](https://insights.sbomify.com/CVE-2016-2148/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28391](https://insights.sbomify.com/CVE-2022-28391/): Command injection in n/a (high 8.8)
- [CVE-2017-16544](https://insights.sbomify.com/CVE-2017-16544/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39810 and fix it if it is affected.

What it is: CVE-2023-39810 is a high-severity path traversal vulnerability in n/a, published on 28 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-39810 in the wild and no public exploit code.

Affected product: n/a. 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-2023-39810/ (Markdown: https://insights.sbomify.com/CVE-2023-39810/index.md)
```

## Sources

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

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