CVE-2026-70469: Apache NiFi: Improper Handling of Case Sensitivity for Content-Encoding in HTTP Requests
Apache NiFi CVE-2026-70469: duplicate or non-standard Content-Encoding headers bypass gzip request filtering in NiFi 2.11.0's REST API.
Memory-exhaustion DoS via crafted Content-Encoding headers in Apache NiFi 2.11.0
Apache NiFi 2.11.0 contains a resource-exhaustion flaw (CWE-409) in the framework enforcement filter that guards the application REST API. Although 2.11.0 disabled gzip request decompression and rejects requests carrying a standard Content-Encoding header identifying gzip, the filter fails to check for multiple instances of the header and does not reject non-standard or case-variant gzip identifiers. A malicious client can therefore submit crafted HTTP requests that bypass the filter and cause the server to decompress payloads, consuming excessive amounts of memory and leading to denial of service. Any deployment running Apache NiFi 2.11.0 with the REST API reachable by untrusted clients is affected, particularly instances exposed to the internet. No public proof-of-concept is known, the flaw is not in CISA KEV, and exploitation has not been confirmed; no CVSS score has been assigned yet.
What to do: Upgrade to Apache NiFi 2.12.0, which disables gzip decompression of HTTP requests regardless of the number of Content-Encoding headers or the encoding identifiers used. Until upgraded, restrict network access to the NiFi REST API so only trusted clients can reach it, and monitor listener memory usage for anomalous spikes that may indicate attempts to trigger the condition.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache NiFi | 2.11.0 (fixed in 2.12.0) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Apache NiFi 2.11.0 disabled support for gzip-encoded HTTP requests for the application REST API and rejected requests that included the standard Content-Encoding header indicating gzip encoding. The framework enforcement filter did not check multiple instances of the Content-Encoding header and did not reject non-standard identifiers for gzip encoding, allowing a malicious client to send crafted requests that could consume excessive amounts of memory. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which disables decompression of gzip-encoded HTTP requests regardless of header number or encoding identifiers.
Apache NiFi CVE-2026-70469: duplicate or non-standard Content-Encoding headers bypass gzip request filtering in NiFi 2.11.0's REST API.
Today 1.6K readers · 2.5K views · 779 reads · all time 189K views