Apache Commons Compress: Denial of service caused by an infinite loop for a corrupted DUMP fileGHSA-4g9r-vxhx-9pgx
MEDIUMGHSA-4g9r-vxhx-9pgx is a medium-severity (CVSS 5.9) CWE-835 vulnerability in org.apache.commons:commons-compress. A fix is available for org.apache.commons:commons-compress — see the affected versions and patch details below.
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-4g9r-vxhx-9pgx.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.commons:commons-compressReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Apache Commons Compress. This issue affects Apache Commons Compress: from 1.3 through 1.25.0.
Users are recommended to upgrade to version 1.26.0 which fixes the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.commons:commons-compress | ≥ 1.3&&< 1.26.0 | 1.26.0org.apache.commons:commons-compress:1.26.0 |
Affected Products
commons compressapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.commons:commons-compress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.commons:commons-compress to 1.26.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4g9r-vxhx-9pgx is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
No mitigation is currently available for this vulnerability.Source: Red Hat security advisory for GHSA-4g9r-vxhx-9pgx (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| CEQ 3.2 | commons-compress | RHSA-2024:1706 |
| Migration Toolkit for Runtimes 1 on RHEL 8 | commons-compress | RHSA-2024:1924 |
| MTA-6.2-RHEL-9 | mta/mta-windup-addon-rhel9:6.2.3-2 | RHSA-2024:3989 |
| Red Hat AMQ Broker 7.13.0 | commons-compress | RHSA-2025:7625 |
| Red Hat AMQ Streams 2.7.0 | see advisory | RHSA-2024:3527 |
| Red Hat build of Quarkus 2.13.9.SP2 | org.apache.commons/commons-compress:1.26.1.redhat-00001 | RHSA-2024:1797 |
| Red Hat build of Quarkus 3.2.11.Final | org.apache.commons/commons-compress:1.26.0.redhat-00001 | RHSA-2024:1662 |
| Red Hat Data Grid | commons-compress | RHSA-2024:1509 |
Frequently Asked Questions
Is GHSA-4g9r-vxhx-9pgx in your dependencies?
Find it across Maven, including transitive dependencies.