How severe is CVE-2012-2098?

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

Which packages are affected by CVE-2012-2098?

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

How do I fix CVE-2012-2098?

Update org.apache.commons:commons-compress to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2098 is resolved across your whole dependency graph.

How do I detect CVE-2012-2098 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-2012-2098 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-2012-2098 actively exploited in the wild?

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

CVE-2012-2098 has an EPSS (Exploit Prediction Scoring System) score of 12.8%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2012-2098?

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

When was CVE-2012-2098 published, and has it been updated?

CVE-2012-2098 was published on June 29, 2012 and was last updated on April 16, 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

CVE-2012-2098 — commons-compress

Fix: apache/commons-compress@020c03d

CVE-2012-2098 is a CWE-310 vulnerability in org.apache.commons:commons-compress. EPSS puts its 30-day exploitation probability at 12.8% (96th percentile). A fix is available for org.apache.commons:commons-compress — see the affected versions and patch details below.

Uncontrolled Resource Consumption in Apache Commons Compress

Also known asGHSA-6fxm-66hq-fc96

Published

Jun 29, 2012

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

12.8%probability of exploitation in next 30 days

Moderate Risk-0.04%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

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

Algorithmic complexity vulnerability in the sorting algorithms in bzip2 compressing stream (BZip2CompressorOutputStream) in Apache Commons Compress before 1.4.1 allows remote attackers to cause a denial of service (CPU consumption) via a file with many repeating inputs.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.commons:commons-compress`	all versions	1.4.1`org.apache.commons:commons-compress:1.4.1`

Affected Products

1 product · 1 configurations

Application

commons compressapache

< 1.4.1

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.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2098 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-2098 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works