# CVE-2025-32799: Conda-build Vulnerable to Path Traversal via Malicious Tar File

> Attackers can exploit path traversal in conda-build to overwrite arbitrary files, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-h499-pxgj-qh5h

## What is CVE-2025-32799?

CVE-2025-32799 is a medium-severity path traversal vulnerability in conda-build, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Conda-build contains commands and tools to build conda packages. Prior to version 25.4.0, the conda-build processing logic is vulnerable to path traversal (Tarslip) attacks due to improper sanitization of tar entry paths. Attackers can craft tar archives containing entries with directory traversal sequences to write files outside the intended extraction directory. This could lead to arbitrary file overwrites, privilege escalation, or code execution if sensitive locations are targeted. This issue has been patched in version 25.4.0.

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

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

It affects 1 product.


Products: Anaconda Conda-Build.

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

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

## Is CVE-2025-32799 being exploited?

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

## Other vulnerabilities in conda-build

- [CVE-2025-32798](https://insights.sbomify.com/CVE-2025-32798/): Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors (high 8.2)
- [CVE-2025-32800](https://insights.sbomify.com/CVE-2025-32800/): Supply chain in conda-build (high 7.2)
- [CVE-2025-32797](https://insights.sbomify.com/CVE-2025-32797/): Conda-build Insecure Build Script Permissions Enabling Arbitrary Code Execution (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32799 and fix it if it is affected.

What it is: CVE-2025-32799 is a medium-severity path traversal vulnerability in conda-build, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32799 exists.

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

## Sources

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

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