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.
CVE-2026-70469
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (1)
Auto-updated Sep 17, 2026Vendor Advisories for CVE-2026-70469(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 05:11 UTCEG score recompute
- 2026-09-19 05:11 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:17 UTCGHSA enrichment
- 2026-09-18 07:22 UTCEG score recompute
- 2026-09-18 07:22 UTCGHSA enrichment
- 2026-09-17 20:28 UTCGHSA enrichment
- 2026-09-17 19:44 UTCEG score recompute▲ 7.50
- 2026-09-17 19:44 UTCGHSA enrichment
- 2026-09-17 19:44 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-09-16 20:25 UTCNVD update
- 2026-09-16 19:44 UTCEG score recompute
- 2026-09-16 19:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-70469?
When was CVE-2026-70469 disclosed?
Is CVE-2026-70469 actively exploited?
What is the CVSS score of CVE-2026-70469?
How do I remediate CVE-2026-70469?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-70469
Is Your Infrastructure Affected by CVE-2026-70469?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.