Skip to content
VulniPulse
High7.5Apache Software Foundation

CVE-2026-47321: Apache MINA: The CompressionFilter class uses ZLib to deflate and inflate data sent and received

This Apache advisory covers CVE-2026-47321. Related products: Apache MINA.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · base score 7.5, scored by apacheAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: high.
Weakness
  • CWE-409: Improper Handling of Highly Compressed Data — Data Amplification
  • CWE-789: Memory Allocation with Excessive Size Value
EPSS
0.49% chance of exploitation in the next 30 days (42nd percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Versions named
Apache MINA 2.2.0 before 2.2.8; Apache MINA 2.1.0 before 2.1.13; Apache MINA 2.0.0 before 2.0.29
Fixed in
2.2.8, 2.1.13, 2.0.29
Source published
Source revised
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Apache Software FoundationUnclassified

Description

The CompressionFilter class uses ZLib to deflate and inflate data sent and received. When we inflate incoming data, the filter does not control the resulting size, and create a buffer no matter what.

Some compressed data may have a compression ration greater than 1 thousand, leading to an exhaustion of the application memory, as we don't control the deflated size.

The fix adds such a control by allowing the application developer to provide a fixed size limit, which when reached throws an exception.

It also allows the user to provide a compression ratio that should not be exceeded, protected the application from small inflated files that inflate in gigantic files, but with a grace limit for the resulting size (1Mb) to avoid false positive (like a very small file inflating with a high ratio, but resulting with a acceptable size, like a few thousands bytes)

For application using this feature, it is highly recommended to create the CompressionFilter and to pass the maximum limit as a forth constructor parameter, maxDecompressedSize:

public CompressionFilter(final boolean compressInbound, final boolean compressOutbound, final int compressionLevel, final int maxDecompressedSize)Optionally one can also provide a maxDecompressRatio fifth parameter, and a decompressRatioMinSize sixth parameter to allow small inflated files with a high compression ratio to still be accepted.

Text from the source record.

Versions named by the source
  • Apache MINA 2.2.0 before 2.2.8
  • Apache MINA 2.1.0 before 2.1.13
  • Apache MINA 2.0.0 before 2.0.29

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-47321

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • The fix adds such a control by allowing the application developer to provide a fixed size limit, which when reached throws an exception.
  • Applications using Apache MINA are advised to upgrade and configure their CompressionFilter instance.

CVE-2026-47321 in other vendors' advisories

Compare every advisory for CVE-2026-47321

Apache Software Foundation advisories, September 2026All Apache Software Foundation advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache