CVE-2024-5569: jaraco/zipp · Loop with Unreachable Exit Condition
Affects jaraco/zippSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium : upgrade to 3.19.1 when convenient.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.19.1
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade jaraco-zipp to 3.19.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIjaraco-zipppkg:pypi/jaraco-zippOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade jaraco/zipp to version 3.19.1 or later to remediate this vulnerability. For applications using the Python standard library zipfile module, ensure that the Python runtime is updated to a version that includes the patched code from jaraco/zipp. Implement strict input validation and sanitization for all zip files processed by applications, especially those uploaded by untrusted users. Employ sandboxing or resource-limiting techniques to isolate processes handling zip files, preventing a single hung process from impacting overall system availability. Monitor application logs and performance metrics for signs of unresponsiveness or infinite loops during zip file processing. Where feasible, restrict the ability to upload or process zip files to trusted users or systems. Additionally, consider implementing timeout mechanisms for file processing operations to recover from potential hangs. Finally, maintain an inventory of all Python dependencies and regularly scan for vulnerable versions to ensure timely patching.
Description
A Denial of Service (DoS) vulnerability exists in the jaraco/zipp library, affecting all versions prior to 3.19.1. The vulnerability is triggered when processing a specially crafted zip file that leads to an infinite loop. This issue also impacts the zipfile module of CPython, as features from the third-party zipp library are later merged into CPython, and the affected code is identical in both projects. The infinite loop can be initiated through the use of functions affecting the `Path` module in both zipp and zipfile, such as `joinpath`, the overloaded division operator, and `iterdir`. Although the infinite loop is not resource exhaustive, it prevents the application from responding. The vulnerability was addressed in version 3.19.1 of jaraco/zipp.