A HIGH-severity vulnerability identified as CVE-2026-47321 has been published on September 21, 2026 with a CVSS base score of 7.5. This security advisory provides a detailed breakdown of the vulnerability, its potential impact, weakness classification, and actionable steps to protect your systems.
Table of Contents
ToggleVulnerability Details
CVE ID: CVE-2026-47321
Severity: HIGH
CVSS Score: 7.5
Published: September 21, 2026
Weakness (CWE): CWE-409
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Confidentiality Impact | None |
| Integrity Impact | None |
| Availability Impact | High |
Technical 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.
Potential Impact
If exploited, this high-severity vulnerability could allow an attacker to cause a denial of service. Organizations running affected software should treat this as a priority remediation item.
Recommended Action
No official patch is available yet. Until one is released:
- Monitor the official NVD page and vendor channels for patch announcements.
- Restrict access to the affected system or service where possible.
- Apply network-level mitigations such as firewall rules or WAF policies.
- Enable logging and alerting for anomalous activity related to this vulnerability.
- Review your incident response plan in case of active exploitation.
References
Related Security Advisories
- [HIGH] CVE-2026-93970 — CVSS 7.3 (September 20, 2026) — HIGH / CVSS 7.3
- [HIGH] CVE-2026-12384 — CVSS 8.8 (September 18, 2026) — HIGH / CVSS 8.8
- [HIGH] CVE-2026-50605 — CVSS 7.4 (September 17, 2026) — HIGH / CVSS 7.4

![[HIGH] CVE-2026-47321 — CVSS 7.5 (September 21, 2026)](https://atlas-cybersecurity.com/wp-content/plugins/elementor/assets/images/placeholder.png)



