# CVE-2025-46394: Information disclosure in BusyBox

> Attackers can hide filenames in TAR archives using terminal escape sequences, potentially concealing malicious content from users.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2025
- **Updated:** 2 Jun 2026
- **Also known as:** ALPINE-CVE-2025-46394, AZL-60936, AZL-61191, BELL-CVE-2025-46394, CLEANSTART-2026-OT80419, DEBIAN-CVE-2025-46394, ECHO-b00e-22b9-2a35, GHSA-wp4q-9jq4-gv74, MINI-7xq4-37v3-672q, OESA-2025-1881, OESA-2025-1882, OESA-2025-1883, UBUNTU-CVE-2025-46394

## What is CVE-2025-46394?

CVE-2025-46394 is a low-severity vulnerability in BusyBox, published on 23 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In tar in BusyBox through 1.37.0, a TAR archive can have filenames hidden from a listing through the use of terminal escape sequences.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information)

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

It affects 1 product.


Products: Busybox Busybox.

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

Upgrade to a fixed version.

## Is CVE-2025-46394 being exploited?

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

## Other vulnerabilities in BusyBox

- [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-2025-46394 and fix it if it is affected.

What it is: CVE-2025-46394 is a low-severity vulnerability in BusyBox, published on 23 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46394 in the wild and no public exploit code.

Affected product: BusyBox. 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-46394/ (Markdown: https://insights.sbomify.com/CVE-2025-46394/index.md)
```

## Sources

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

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