How severe is GHSA-q53q-5r4j-5729?

No CVSS score has been assigned to GHSA-q53q-5r4j-5729 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q53q-5r4j-5729?

GHSA-q53q-5r4j-5729 affects the following packages: rattler (crates.io), py-rattler (PyPI). Ecosystems affected: crates.io, PyPI.

How do I fix GHSA-q53q-5r4j-5729?

Update rattler to 0.43.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q53q-5r4j-5729 is resolved across your whole dependency graph.

How do I detect GHSA-q53q-5r4j-5729 in my crates.io, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rattler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q53q-5r4j-5729 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-q53q-5r4j-5729 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q53q-5r4j-5729 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q53q-5r4j-5729?

GHSA-q53q-5r4j-5729 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q53q-5r4j-5729?

GHSA-q53q-5r4j-5729 is classified as Path Traversal (CWE-22), CWE-73 (CWE-73). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-q53q-5r4j-5729 published, and has it been updated?

GHSA-q53q-5r4j-5729 was published on June 1, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io🐍 PyPI

Not in CISA KEV

rattler has an entry-point path traversal in noarch:python install (arbitrary file write)GHSA-q53q-5r4j-5729

Fix: conda/rattler#2445

GHSA-q53q-5r4j-5729 is a Path Traversal vulnerability in rattler. A fix is available for rattler — see the affected versions and patch details below.

Also known asCVE-2026-47425PYSEC-2026-2971

Published

Jun 1, 2026

Updated

Jul 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q53q-5r4j-5729.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🦀rattler🐍py-rattler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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, 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 @ e640477
pixi 0.69.0 and rattler-build 0.65.0 fix this issue

Researcher

Berkant Koc [email protected] PGP: 0C588DFD76204987284213EA0AC529C41F8AA5D6

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rattler`	all versions	0.43.2`cargo update -p rattler --precise 0.43.2`
🐍PyPI	`py-rattler`	all versions	0.24.0`pip install --upgrade 'py-rattler==0.24.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rattler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rattler to 0.43.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q53q-5r4j-5729 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

## Summary `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`, `rattler-build`, some meth

O3 Security · Impact-Aware SCA

Is GHSA-q53q-5r4j-5729 in your dependencies?

Find it across crates.io, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

rattler has an entry-point path traversal in noarch:python install (arbitrary file write)GHSA-q53q-5r4j-5729

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Affected

Researcher

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-q53q-5r4j-5729 in your dependencies?