Medium, CVSS 6.3crates.ioAmendedPublished
rattler has an entry-point path traversal in noarch:python install (arbitrary file write)
CVE-2026-47425 · GHSA-q53q-5r4j-5729
- Affected
- crates.io rattler < 0.43.2
- Fixed in
- 0.43.2· Vendor fix available
- Issue
- EntryPoint::FromStr in rattlercondatypes 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, rattler-build, some methods in py-rattler, and any other consumer of the rattler install crate; no flag or post-link-script opt-in is involved. Resolved in https://github.com/conda/rattler/pull/2445, released in rattler 0.43.2. Affected - Repository: https://github.com/conda/rattler - Commit: a0e61a33da8b9d6de712fab2a879fa9da977e6e3 (HEAD at audit time, 2026-05-13 release) - Downstream consumers reached through the same code path: prefix-dev/pixi @…
Recommended action: Upgrade to 0.43.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.