CVE-2026-47321
CVE-2026-47321 · Apache MINA: Unbounded Decompression Amplification DoS in Zlib.inflate
CVSS 7.5 · High · EPSS 0.5% · Fix available
Compare with your installed version
Affected products and known fixed versions are public information. Compare them with your installed version.
- apache minaUpdate to 2.0.29 / 2.1.13 / 2.2.8
- mina Debian 12No fix published
- mina2 Debian 12No fix published
- mina2 Debian 13No fix published
- and 14 more
Check the installed version:
dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="mina"'dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="mina2"'Assess your server’s risks
The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.
Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.
curl -fsSL https://patchfirst.dev/check.sh | shChannels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
- Published
- Updated
Stack: system
Affected products and versions
apache mina
- Versions
- ≥ 2.2.0, < 2.2.8: Affected (maven)
- ≥ 2.1.0, < 2.1.13: Affected (maven)
- ≥ 2.0.0, < 2.0.29: Affected (maven)
Update to 2.0.29; Update to 2.1.13; Update to 2.2.8
mina Debian 12
- Versions
- 1.1.7.dfsg-13
- 1.1.7.dfsg-14
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Debian 12
- Versions
- 2.2.1-3
- 2.2.1-4
- 2.2.9-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Debian 13
- Versions
- 2.2.1-4
- 2.2.9-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Debian 14
- Versions
- 2.2.1-4
- Affected ranges
- ECOSYSTEM: < 2.2.9-1
Update to 2.2.9-1
mina Ubuntu 16.04 LTS
- Versions
- 1.1.7.dfsg-11
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu 16.04 LTS
- Versions
- 2.0.7+dfsg-2
- 2.0.9-1
- 2.0.9-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina Ubuntu 18.04 LTS
- Versions
- 1.1.7.dfsg-11
- 1.1.7.dfsg-12
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu 18.04 LTS
- Versions
- 2.0.16-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina Ubuntu 20.04 LTS
- Versions
- 1.1.7.dfsg-13
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu 20.04 LTS
- Versions
- 2.0.19-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina Ubuntu 22.04 LTS
- Versions
- 1.1.7.dfsg-13
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu Pro 22.04 LTS
- Versions
- 2.1.4-2
- 2.1.5-1
- 2.1.5-1ubuntu0.1~esm1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina Ubuntu 24.04 LTS
- Versions
- 1.1.7.dfsg-13
- 1.1.7.dfsg-13ubuntu1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu Pro 24.04 LTS
- Versions
- 2.2.1-3
- 2.2.1-3ubuntu0.1~esm1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu 25.10
- Versions
- 2.2.1-3
- 2.2.1-4
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu 26.10
- Versions
- 2.2.1-4
- 2.2.1-4ubuntu1
- 2.2.9-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
mina2 Ubuntu Pro 26.04 LTS
- Versions
- 2.2.1-4
- 2.2.1-4ubuntu0.1~esm1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published