Path Traversal in rattler (CVE-2026-47425)
Summary
Path traversal in rattler (CVE-2026-47425). Risk of unauthorized operations or information disclosure. Exploitable via rattler_conda_types. Mitigation: upgrade to 0.43.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47425 has been found in rattler.
Attackers can target a specific entry point like rattler_conda_types over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade rattler to 0.43.2 or later.
If unsure, ask your IT team or search "rattler CVE-2026-47425" on the vendor's site.
CVE-2026-47425 (rattler) — CWE-22
Attack surface: rattler_conda_types / command / rattler / a0e61a33da8b9d6de712fab2a879fa9da977e6e3
Patched: 0.43.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in rattler. Attackers reach the vulnerable code path via rattler_conda_types.
Check the vendor advisory for the affected versions of rattler. Attack surface: rattler_conda_types / command / rattler / a0e61a33da8b9d6de712fab2a879fa9da977e6e3.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.43.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'rattler' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'rattler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rattlerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade rattler to 0.43.2ステージング環境で 0.43.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com