Low

Authorization bypass in Apache NiFi Parameter Context asset deletion

IdentifiersCVE-2026-68980CWE-863· Incorrect Authorization

CVE-2026-68980 is an improper authorization vulnerability in Apache NiFi nifi-web-api affecting versions 2.0.0 through 2.10.0. Apache NiFi supports creating, reading, and deleting Assets associated with Parameter Contexts through its REST API. In the vulnerable deletion path, the framework authorized asset deletion using a supplied Parameter Context identifier together with the Asset identifier, but did not verify that the supplied Parameter Context identifier matched the stored owner identifier of the requested Asset. This created an authorization gap in which deletion checks were performed against attacker-controlled context input rather than the actual ownership relationship of the Asset. Apache NiFi 2.11.0 corrects this by validating Parameter Context ownership before deletion using the same approach already applied to Asset read operations.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an authenticated user with write access in one Parameter Context to delete an Asset associated with a different Parameter Context if the deployment enforces different authorization levels across Parameter Contexts. The primary impact is unauthorized modification of application state through deletion of Assets outside the attacker's intended authorization scope, which can disrupt configuration management and operations dependent on those Assets. The issue is low severity and does not materially affect deployments where Parameter Contexts do not have differentiated authorization boundaries.

Mitigation

If you can’t patch tonight, do this now.

Apply the vendor fix by upgrading to Apache NiFi 2.11.0 or later. Where immediate upgrade is not possible, reduce exposure by avoiding differentiated authorization levels across Parameter Contexts for users who can invoke the affected REST API deletion operation, since deployments without such authorization separation are not subject to the vulnerability in practice.

Remediation

Patch, then assume compromise.

Upgrade Apache NiFi to version 2.11.0 or later. The fixed release verifies that the requested Asset is actually owned by the Parameter Context used for authorization before permitting deletion.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Apache Software FoundationNifiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

1 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1