Skip to content

CVE-2026-68980

Apache Nifi broken access control

9.1 CRITICALEPSS 0.48%
  1. Published3 Aug 2026

Description

Apache NiFi 2.0.0 through 2.10.0 support creating, reading, and deleting Assets associated with Parameter Contexts through the REST API. The framework authorizes asset deletion against the owning Parameter Context using the supplied Parameter Context Identifier and Asset Identifier. The framework performed authorized based on the supplied Parameter Context Identifier without verifying the requested Identifier against the stored Identifier. Apache NiFi installations that do not implement different levels of authorization across Parameter Contexts are not subject to this vulnerability, because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.11.0 is the recommended mitigation, which verifies Parameter Context ownership of the requested Asset before deletion using the same strategy applied to Asset read operations.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Apache Nifi≥ 2.0.0 < 2.11.0

Remediation

Fixed in
Apache Nifi≥ 2.11.0

Frequently asked

Is CVE-2026-68980 being actively exploited?

CVE-2026-68980 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.48%.

How severe is CVE-2026-68980?

CVE-2026-68980 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.48% probability of exploitation.

Which products are affected by CVE-2026-68980?

Affected products include Apache Nifi.

How do I fix CVE-2026-68980?

Upgrade affected software to a fixed version, for example Apache Nifi 2.11.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-68980 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.