Apache NiFi: Improper Handling of Case Sensitivity for Content-Encoding in HTTP Requests (CVE-2026-70469) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-70469

Apache NiFi: Improper Handling of Case Sensitivity for Content-Encoding in HTTP Requests

Answer in brief

CVE-2026-70469 records a Unknown severity vulnerability in Apache NiFi: Improper Handling of Case Sensitivity for Content-Encoding in HTTP Requests. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/Apache NiFi (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Apache Software Foundation/Apache NiFi (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Apache Software Foundation/Apache NiFigeneric	2.11.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Apache Software Foundation/Apache NiFi.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Source referencelists.apache.org

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.