# CVE-2026-47425: Rattler vulnerable to entry-point path traversal in noarch:python install (arbitrary file write)

> A malicious Conda package can write arbitrary files outside the installation prefix via path traversal in entry-point handling, potentially leading to code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA: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:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-q53q-5r4j-5729, PYSEC-2026-2971

## What is CVE-2026-47425?

CVE-2026-47425 is a medium-severity path traversal vulnerability in conda pixi, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Rattler is a library that provides common functionality used within the conda ecosystem. Prior to version 0.43.2, `EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `mamba install` via py-rattler, `rattler-build`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved. Version 0.43.2 contains a fix for the issue.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-47425?

5 open source packages ship an affected version, including py-rattler and rattler.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `py-rattler` | PyPI | All versions | 0.24.0 |
| `py-rattler` | PyPI | All versions | 0.24.0 |
| `py-rattler` | PyPI | All versions | 0.24.0 |
| `rattler` | crates.io | All versions | 0.43.2 |
| `rattler` | crates.io | All versions | 0.43.2 |

## How do I fix CVE-2026-47425?

Upgrade py-rattler to 0.24.0 or later.

## Is CVE-2026-47425 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47425 and fix it if it is affected.

What it is: CVE-2026-47425 is a medium-severity path traversal vulnerability in conda pixi, published on 21 Jul 2026. 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-2026-47425 in the wild and no public exploit code.

Affected packages and fixed versions:
- py-rattler (PyPI): affected all versions; fixed in 0.24.0
- py-rattler (PyPI): affected all versions; fixed in 0.24.0
- py-rattler (PyPI): affected all versions; fixed in 0.24.0
- rattler (crates.io): affected all versions; fixed in 0.43.2
- rattler (crates.io): affected all versions; fixed in 0.43.2

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

## Sources

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

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