Rattler, a common library in the Conda ecosystem, allowed the build string from package metadata to be incorporated into a cache path during materialization. A malicious or untrusted channel could embed path separators or traversal characters in that field, causing files to be written outside the intended cache directory. This flaw can lead to overwriting critical files or inserting malicious content into the Conda environment, thereby compromising integrity and potentially allowing privilege escalation if an attacker gains write access to sensitive locations.

The vulnerability affects the rattler_cache component before version 0.9.0 and the py-rattler component before version 0.24.0. Any installation using these older versions and consuming packages from channels that are not curated by the official Conda team is at risk. The issue is confined to systems that rely on the default package cache path handling in these libraries.

The CVSS score of 5.4 indicates a moderate severity. There is no EPSS score available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires a malicious or untrusted Conda channel to publish repodata containing a crafted build string; curated channels validate metadata and should not allow such malformed entries. The attack vector is therefore limited to compromised or fraudulent channels rather than arbitrary network exposure.