Skip to content
VulniPulse
High 2 vendors · 2 advisories

CVE-2026-47321: Apache MINA: Unbounded Decompression Amplification DoS in Zlib.inflate

CVE-2026-47321 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
7.5 (Apache), 7.5 (Red Hat)
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, .
Fixed releases
  • Apache: 2.2.8, 2.1.13, 2.0.29
Vendor advisories
2 from Apache, Red Hat
Assigned by
apache (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-47321; each belongs to its advisory, not to every product listed. How records are collected and checked.

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. Here are the additional constructor: public CompressionFilter(final boolean compressInbound, final boolean compressOutbound, final int compressionLevel, final int maxDecompressedSize, final long maxDecompressRatio, final long decompressRatioMinSize) Also note that a fluent API has been added to spare the users the pain to call a constructor with that many parameters: CompressionFilter compressionFilter = new CompressionFilter() .setCompressionLevel(Zlib.COMPRESSION_MAX) .setMaxDecompressedSize(1_000_000) .setMaxDecompressRatio(100). .setDecompressRatioMinSize(100_000); Applications using Apache MINA are advised to upgrade and configure their CompressionFilter instance.

Text from the CVE.org record (apache).

How do I fix CVE-2026-47321?

Upgrade to a fixed release named by the vendor:

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

Vendor advisories for CVE-2026-47321

Apache

1 advisory
  • Advisory severityHigh7.5

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

    CVE-2026-47321Source published Source updated

    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…

    Related products — impact not confirmed
    • Apache MINA
    Source-reported affected versions
    • 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
    Source-reported fixed versions
    • 2.2.8
    • 2.1.13
    • 2.0.29
    Mitigation 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.

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-47321] Denial of Service via unbounded decompression amplification

    CVE-2026-47321Source published Source updated

    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…

    Affected products in this advisory
    • OpenShift Developer Tools and Services
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 9
    • Red Hat Fuse 7

    1 more entries in the full advisory.

    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All Apache 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