CVE-2026-53956: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in conda rattler_cache
Rattler is a library that provides common functionality used within the conda ecosystem. `rattler_cache` prior to version 0.9.0 and `py-rattler` prior to version 0.24.0 were vulnerable to package-cache path traversal when handling package metadata from conda channels. During cache materialization, the `ratter_cache` code used the package record `build` string as part of a cache key that was joined into a filesystem path. A malicious or untrusted channel could publish repodata with path separators or traversal components in that field, causing package contents to be written outside the configured package cache directory. The issue requires use of a malicious or otherwise untrusted conda channel. Curated channels that validate package metadata are not expected to allow malformed build strings of this form. Users should upgrade to `rattler_cache` version 0.9.0 or `py-rattler` version 0.24.0 and avoid untrusted conda channels.
AI Analysis
Technical Summary
Rattler is a library used within the conda ecosystem. Versions of rattler_cache before 0.9.0 and py-rattler before 0.24.0 are vulnerable to a package-cache path traversal vulnerability (CVE-2026-53956). The vulnerability arises because the package record's build string is used as part of a cache key that is joined into a filesystem path without proper sanitization. A malicious conda channel could publish repodata with path separators or traversal sequences in the build string, causing files to be written outside the configured package cache directory. This can lead to integrity issues with the package cache. The issue requires a malicious or untrusted channel; curated channels that validate package metadata are not expected to allow such malformed build strings.
Potential Impact
The vulnerability allows an attacker controlling or influencing a conda channel to cause package contents to be written outside the intended package cache directory via path traversal in the build string. This could lead to integrity issues or potential denial of service by overwriting files outside the cache. There is no indication of confidentiality or direct code execution impact. The attack requires user interaction with a malicious or untrusted channel.
Mitigation Recommendations
A patch is available. Users should upgrade to rattler_cache version 0.9.0 or later and py-rattler version 0.24.0 or later. Additionally, users should avoid using untrusted or malicious conda channels, as curated channels that validate package metadata are not expected to allow malformed build strings. No other mitigation is indicated.
CVE-2026-53956: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in conda rattler_cache
Description
Rattler is a library that provides common functionality used within the conda ecosystem. `rattler_cache` prior to version 0.9.0 and `py-rattler` prior to version 0.24.0 were vulnerable to package-cache path traversal when handling package metadata from conda channels. During cache materialization, the `ratter_cache` code used the package record `build` string as part of a cache key that was joined into a filesystem path. A malicious or untrusted channel could publish repodata with path separators or traversal components in that field, causing package contents to be written outside the configured package cache directory. The issue requires use of a malicious or otherwise untrusted conda channel. Curated channels that validate package metadata are not expected to allow malformed build strings of this form. Users should upgrade to `rattler_cache` version 0.9.0 or `py-rattler` version 0.24.0 and avoid untrusted conda channels.
CVSS v3.1
Score 5.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Rattler is a library used within the conda ecosystem. Versions of rattler_cache before 0.9.0 and py-rattler before 0.24.0 are vulnerable to a package-cache path traversal vulnerability (CVE-2026-53956). The vulnerability arises because the package record's build string is used as part of a cache key that is joined into a filesystem path without proper sanitization. A malicious conda channel could publish repodata with path separators or traversal sequences in the build string, causing files to be written outside the configured package cache directory. This can lead to integrity issues with the package cache. The issue requires a malicious or untrusted channel; curated channels that validate package metadata are not expected to allow such malformed build strings.
Potential Impact
The vulnerability allows an attacker controlling or influencing a conda channel to cause package contents to be written outside the intended package cache directory via path traversal in the build string. This could lead to integrity issues or potential denial of service by overwriting files outside the cache. There is no indication of confidentiality or direct code execution impact. The attack requires user interaction with a malicious or untrusted channel.
Mitigation Recommendations
A patch is available. Users should upgrade to rattler_cache version 0.9.0 or later and py-rattler version 0.24.0 or later. Additionally, users should avoid using untrusted or malicious conda channels, as curated channels that validate package metadata are not expected to allow malformed build strings. No other mitigation is indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-h672-p7h7-97v9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53956"]
- Ecosystems
- ["crates.io","PyPI"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a50ba3c68715ace4357db21
Added to database: 07/10/2026, 09:24:12 UTC
Last enriched: 09/10/2026, 11:06:58 UTC
Last updated: 09/14/2026, 19:56:45 UTC
Views: 81
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.