Cross-context asset deletion via unchecked ownership identifier
Published Aug 3, 2026 · Updated Aug 3, 2026
Incorrect authorization in Apache NiFi 2.0.0 through 2.10.0 allows remote authenticated users to delete assets across Parameter Contexts. The StandardNiFiServiceFacade.verifyDeleteAsset() method authorizes the supplied Parameter Context ID but does not compare it with the Asset's stored owner ID. Exploitation requires write access to one Parameter Context and different authorization levels across contexts; successful requests delete assets owned by another context.
Summary
What happened
Incorrect authorization in Apache NiFi 2.0.0 through 2.10.0 allows remote authenticated users to delete assets across Parameter Contexts. The StandardNiFiServiceFacade.verifyDeleteAsset() method authorizes the supplied Parameter Context ID but does not compare it with the Asset's stored owner ID. Exploitation requires write access to one Parameter Context and different authorization levels across contexts; successful requests delete assets owned by another context.
The record
- CVE
- CVE-2026-68980
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache NiFi
- Classifications
- CWE-863, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <=2.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo