No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 18 Sep 2026 04:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache nifi |
|
| Vendors & Products |
Apache
Apache nifi |
Thu, 17 Sep 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 16 Sep 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 16 Sep 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache NiFi: Improper Handling of Case Sensitivity for Content-Encoding in HTTP Requests | |
| Weaknesses | CWE-409 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-09-17T19:38:26.785Z
Reserved: 2026-08-04T15:09:34.902Z
Link: CVE-2026-70469
Updated: 2026-09-17T19:38:23.503Z
Status : Undergoing Analysis
Published: 2026-09-16T20:17:26.877
Modified: 2026-09-17T20:18:00.007
Link: CVE-2026-70469
No data.
OpenCVE Enrichment
Updated: 2026-09-18T03:45:01Z