GHSA-9mqm-qcwf-5qhg: CredSweeper: Recursive archive size-limit bypass in deep scanner allows crafted compressed inputs to exhaust resources
CredSweeper versions 1.4.9 up to but not including 1.16.0 contain a vulnerability in the deep scanner's recursive archive size-limit enforcement. The scanner does not properly enforce the recursive size budget, allowing crafted compressed inputs such as gzip, bzip2, lzma/xz, zip, and tar archives to bypass intended zip-bomb protections. This can lead to excessive memory and CPU consumption during deep scanning when enabled. The vulnerability does not allow code execution, file writes, or data exfiltration but impacts availability by exhausting resources.
AI Analysis
Technical Summary
CredSweeper's deep scanner fails to enforce the recursive size limit as a hard stop, allowing crafted compressed archives to bypass zip-bomb protections. Single-stream decompressors (gzip, bzip2, lzma/xz) fully decompress data before checking the size budget, and recursive scanning continues even if the budget is negative. Multi-entry archives (zip, tar, rpm) check each entry against the original per-entry budget rather than a cumulative budget, enabling multiple small entries to collectively exceed the limit. This results in resource exhaustion (memory and CPU) during deep scanning with recursive depth enabled. The issue affects CredSweeper versions >=1.4.9 and <1.16.0. There is no evidence of arbitrary code execution or data compromise.
Potential Impact
The vulnerability allows attackers to craft compressed archives that bypass the recursive size limit checks, causing CredSweeper's deep scanner to consume excessive system resources (memory and CPU). This leads to denial of service conditions by exhausting availability. There is no confirmed impact on confidentiality or integrity, such as code execution or data leakage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider disabling deep scanning with recursive depth enabled or limiting the size and complexity of scanned archives to reduce risk of resource exhaustion. Monitor for updates from the CredSweeper project regarding an official fix.
GHSA-9mqm-qcwf-5qhg: CredSweeper: Recursive archive size-limit bypass in deep scanner allows crafted compressed inputs to exhaust resources
Description
CredSweeper versions 1.4.9 up to but not including 1.16.0 contain a vulnerability in the deep scanner's recursive archive size-limit enforcement. The scanner does not properly enforce the recursive size budget, allowing crafted compressed inputs such as gzip, bzip2, lzma/xz, zip, and tar archives to bypass intended zip-bomb protections. This can lead to excessive memory and CPU consumption during deep scanning when enabled. The vulnerability does not allow code execution, file writes, or data exfiltration but impacts availability by exhausting resources.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CredSweeper's deep scanner fails to enforce the recursive size limit as a hard stop, allowing crafted compressed archives to bypass zip-bomb protections. Single-stream decompressors (gzip, bzip2, lzma/xz) fully decompress data before checking the size budget, and recursive scanning continues even if the budget is negative. Multi-entry archives (zip, tar, rpm) check each entry against the original per-entry budget rather than a cumulative budget, enabling multiple small entries to collectively exceed the limit. This results in resource exhaustion (memory and CPU) during deep scanning with recursive depth enabled. The issue affects CredSweeper versions >=1.4.9 and <1.16.0. There is no evidence of arbitrary code execution or data compromise.
Potential Impact
The vulnerability allows attackers to craft compressed archives that bypass the recursive size limit checks, causing CredSweeper's deep scanner to consume excessive system resources (memory and CPU). This leads to denial of service conditions by exhausting availability. There is no confirmed impact on confidentiality or integrity, such as code execution or data leakage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider disabling deep scanning with recursive depth enabled or limiting the size and complexity of scanned archives to reduce risk of resource exhaustion. Monitor for updates from the CredSweeper project regarding an official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9mqm-qcwf-5qhg
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a520eb668715ace438f52f4
Added to database: 07/11/2026, 09:36:54 UTC
Last enriched: 07/11/2026, 09:50:54 UTC
Last updated: 07/11/2026, 23:43:21 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.