EXPOSURES › CVE-2026-68980
CVE-2026-68980
CRITICALApache NiFi 2.0.0-2.10.0 allows unauthenticated deletion of assets via REST API due to missing identifier verification.
Apache NiFi failed to verify the requested Parameter Context Identifier against the stored one during asset deletion, enabling unauthorized data manipulation. DIB orgs must upgrade to 2.11.0 immediately to prevent data integrity breaches and compliance violations under NIST 800-171.
Shame score — A critical authorization bypass in a widely deployed data integration tool that allows unauthenticated deletion of assets, representing a significant data integrity and compliance risk.
▸ RECOMMENDED ACTION Critical severity — schedule patching of the affected products.
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.