Arbitrary file write via unvalidated build string
Published Sep 9, 2026 · Updated Sep 10, 2026
Path traversal in Conda py-rattler before 0.24.0 and rattler_cache before 0.9.0 allows attackers to write files outside the package cache. During cache materialization, the cache key joins an unvalidated package-record build string into a filesystem path, allowing traversal components to escape the configured cache directory. Exploitation requires use of a malicious or untrusted conda channel and permits writes with the consuming process's filesystem privileges.
Summary
What happened
Path traversal in Conda py-rattler before 0.24.0 and rattler_cache before 0.9.0 allows attackers to write files outside the package cache. During cache materialization, the cache key joins an unvalidated package-record build string into a filesystem path, allowing traversal components to escape the configured cache directory. Exploitation requires use of a malicious or untrusted conda channel and permits writes with the consuming process's filesystem privileges.
The record
- CVE
- CVE-2026-53956
- Published
- Sep 9, 2026
- Updated
- Sep 10, 2026
- Vendor
- Conda
- Product
- py-rattler
- Classifications
- CWE-73, CWE-22, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.24.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo