Skip to content
Applications

CVE-2026-68981

HIGH
High
EPSS 0.52%Patch availableAug 4, 2026

Apache NiFi gzip decompression flaw allows remote memory exhaustion (DoS) in NiFi <=2.10.0

common questions

Is CVE-2026-68981 being exploited?

Not confirmed. CVE-2026-68981 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-68981?

CVE-2026-68981 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-68981?

Yes. A fix has been recorded for CVE-2026-68981. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-68981 affect?

CVE-2026-68981 affects Apache NiFi 1.5.0 - 2.10.0, NiFi REST API endpoints handling gzip requests. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-68981?

Upgrade NiFi to 2.11.0; block untrusted clients and enforce request size limits at network edge.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache NiFi 1.5.0 - 2.10.0NiFi REST API endpoints handling gzip requests
impact

Remote memory exhaustion via crafted gzip-encoded REST API requests that bypass compressed-size limits, causing OOM, service crash and denial of service.

action required

Immediate action required

affected versions
Apache Software Foundation Apache NiFi
  • affected>= 1.5.0 and <= 2.10.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free