How severe is CVE-2024-25710?

CVE-2024-25710 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-25710?

CVE-2024-25710 affects the following packages: org.apache.commons:commons-compress (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-25710?

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 CVE-2024-25710 is resolved across your whole dependency graph.

How do I detect CVE-2024-25710 in my Maven dependencies?

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.

How do I mitigate CVE-2024-25710 if there is no patch (or I can't update yet)?

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.

Is CVE-2024-25710 actively exploited in the wild?

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

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

CVE-2024-25710 is classified as CWE-835 (CWE-835). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-25710 published, and has it been updated?

CVE-2024-25710 was published on February 19, 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.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2024-25710 — commons-compress

HIGH

CVE-2024-25710 is a high-severity (CVSS 8.1) 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.

Apache Commons Compress: Denial of service caused by an infinite loop for a corrupted DUMP file

Also known asGHSA-4g9r-vxhx-9pgx

Published

Feb 19, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 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 CVE-2024-25710.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

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

1 pkg affected

☕org.apache.commons:commons-compress

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.commons:commons-compress`	≥ 1.3&&< 1.26.0	1.26.0`org.apache.commons:commons-compress:1.26.0`

Affected Products

1 product · 1 configurations

Application

commons compressapache

≥ 1.3 && < 1.26.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2024-25710 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.

Red HatModerate

Workaround published by Red Hat

No mitigation is currently available for this vulnerability.

Source: Red Hat security advisory for CVE-2024-25710 (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

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.

O3 Security · Impact-Aware SCA

Is CVE-2024-25710 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

CWE Classification

CWE-835CWE-835

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

commons-compress

8.3/10

Maintained10/10

Code-Review0/10

Dependency-Update-Tool10/10

Branch-Protection3/10

Vulnerabilities9/10

Assessed Nov 9, 2026

Timeline

Disclosed

Feb 19, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2024-25710

GHSA-4g9r-vxhx-9pgx

References

Advisorygithub.com · CVE 2024 25710.json Advisorylists.apache.org · cz8qkcwphy4cx8gltn932ln51cbtq6kf Advisorynvd.nist.gov · CVE 2024 25710 Advisorysecurity.netapp.com · ntap 20240307 0010 Webseclists.org Webopenwall.com Webrepo.maven.apache.org · maven2 Websecurity.netapp.com · ntap 20240307 0010 Packagegithub.com · commons compress

Related vulnerabilities

This CVE is high severity; 5 of 8 other CVEs affecting commons-compress are rated as high or higher (top: high).

CVE-2024-26308CVE-2023-42503CVE-2012-2098CVE-2021-35515CVE-2021-35516CVE-2021-36090CVE-2021-35517CVE-2019-12402

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2024-25710 — commons-compress

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2024-25710 in your dependencies?