Apache NiFi 1.52.10: Gzipdecoded REST API Memory Exhaustion
CVE-2026-68981 Published on August 3, 2026
Apache NiFi: Uncontrolled Resource Consumption through Decompression of HTTP Requests
Apache NiFi 1.5.0 through 2.10.0 support gzip-encoded HTTP requests for the application REST API using a Jersey encoding filter. The framework enforced a configurable maximum request size on the compressed payload rather than the decompressed output, allowing a malicious client to send crafted requests that could consume excessive amounts of memory. Upgrading to Apache NiFi 2.11.0 is the recommended mitigation, which relocates response compression to Jetty Server and disables decompression of gzip-encoded HTTP requests.
Vulnerability Analysis
CVE-2026-68981 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.
Timeline
reported
Weakness Type
What is a Data Amplification Vulnerability?
The software does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output. An example of data amplification is a "decompression bomb," a small ZIP file that can produce a large amount of data when it is decompressed.
CVE-2026-68981 has been classified to as a Data Amplification vulnerability or weakness.
Products Associated with CVE-2026-68981
Want to know whenever a new CVE is published for Apache NiFi? stack.watch will email you.
Affected Versions
Apache Software Foundation Apache NiFi:- Version 1.5.0, <= 2.10.0 is affected.