How severe is CVE-2024-21542?

No CVSS score has been assigned to CVE-2024-21542 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-21542?

CVE-2024-21542 affects the following packages: luigi (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-21542?

Update luigi to 3.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-21542 is resolved across your whole dependency graph.

How do I detect CVE-2024-21542 in my PyPI dependencies?

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

How do I mitigate CVE-2024-21542 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 CVE-2024-21542 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-21542 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 CVE-2024-21542?

CVE-2024-21542 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 67th 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 CVE-2024-21542?

CVE-2024-21542 is classified as CWE-29 (CWE-29), Path Traversal (CWE-22). 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 CVE-2024-21542 published, and has it been updated?

CVE-2024-21542 was published on December 10, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2024-21542 — luigi

Fix: spotify/luigi@b5d1b96

CVE-2024-21542 is a CWE-29 vulnerability in luigi. A fix is available for luigi — see the affected versions and patch details below.

luigi Arbitrary File Write via Archive Extraction (Zip Slip)

Also known asGHSA-8qch-vj6m-2694PYSEC-2024-159

Published

Dec 10, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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 CVE-2024-21542.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍luigi

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

Description

Versions of the package luigi before 3.6.0 are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) due to improper destination file path validation in the _extract_packages_archive function.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`luigi`	all versions	3.6.0`pip install --upgrade 'luigi==3.6.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for luigi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update luigi to 3.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-21542 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

O3 Security · Impact-Aware SCA

Is CVE-2024-21542 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works