CVE-2026-81866: CWE-862 Missing Authorization in Apache Software Foundation Apache NiFi
Apache NiFi 2.9.0 through 2.11.0 provide Connector configuration update and verification REST API methods that do not enforce authorization checking on Assets and Secrets referenced in proposed configuration. Updating or verifying a Connector configuration step can apply Asset and Secret references, but framework authorization was limited to write privileges on the Connector itself. As a result of the missing authorization, an authenticated user authorized to modify a Connector, but not authorized to read a referenced Parameter Provider, could apply Secret values backed by that Parameter Provider. The same methods also accepted Asset identifiers without verifying that the Asset belonged to the Connector being configured. Apache NiFi installations that do not implement different levels of authorization across Connectors and Parameter Providers are not subject to this vulnerability, because the framework enforces write permissions on the Connector as the security boundary. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which authorizes read access to referenced Parameter Providers and verifies Connector ownership of referenced Assets during configuration update and verification.
AI Analysis
Technical Summary
CVE-2026-81866 describes a missing authorization vulnerability (CWE-862) in Apache NiFi versions 2.9.0 through 2.11.0. The Connector configuration update and verification REST API methods allow authenticated users with write privileges on a Connector to apply Asset and Secret references without proper authorization checks on the referenced Parameter Providers or Assets. This means users can apply Secret values backed by Parameter Providers they cannot read and reference Assets not owned by the Connector. The vulnerability arises because authorization was limited to write privileges on the Connector itself, not on the referenced resources. Apache NiFi installations that do not differentiate authorization levels across Connectors and Parameter Providers are not affected. The issue is addressed in Apache NiFi 2.12.0, which adds authorization checks for read access to Parameter Providers and verifies Asset ownership during configuration updates.
Potential Impact
An authenticated user with write privileges on a Connector but without read authorization on referenced Parameter Providers can apply Secret values from those Parameter Providers. This could lead to unauthorized use of Secrets in Connector configurations. Additionally, Assets can be referenced without verifying ownership, potentially allowing unauthorized Asset usage. The impact is limited by the requirement for authenticated users with write access to the Connector, and installations with uniform authorization across Connectors and Parameter Providers are not affected.
Mitigation Recommendations
Upgrade Apache NiFi to version 2.12.0 or later. This version enforces read access authorization on referenced Parameter Providers and verifies that referenced Assets belong to the Connector being configured during configuration update and verification. No other mitigation actions are specified or required.
CVE-2026-81866: CWE-862 Missing Authorization in Apache Software Foundation Apache NiFi
Description
Apache NiFi 2.9.0 through 2.11.0 provide Connector configuration update and verification REST API methods that do not enforce authorization checking on Assets and Secrets referenced in proposed configuration. Updating or verifying a Connector configuration step can apply Asset and Secret references, but framework authorization was limited to write privileges on the Connector itself. As a result of the missing authorization, an authenticated user authorized to modify a Connector, but not authorized to read a referenced Parameter Provider, could apply Secret values backed by that Parameter Provider. The same methods also accepted Asset identifiers without verifying that the Asset belonged to the Connector being configured. Apache NiFi installations that do not implement different levels of authorization across Connectors and Parameter Providers are not subject to this vulnerability, because the framework enforces write permissions on the Connector as the security boundary. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which authorizes read access to referenced Parameter Providers and verifies Connector ownership of referenced Assets during configuration update and verification.
CVSS v4.0
Score 0.5low
Affected software
Apache Software Foundation
Apache NiFi
pkg:maven/Apache Software Foundation/org.apache.nifi:nifi-web-apiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-81866 describes a missing authorization vulnerability (CWE-862) in Apache NiFi versions 2.9.0 through 2.11.0. The Connector configuration update and verification REST API methods allow authenticated users with write privileges on a Connector to apply Asset and Secret references without proper authorization checks on the referenced Parameter Providers or Assets. This means users can apply Secret values backed by Parameter Providers they cannot read and reference Assets not owned by the Connector. The vulnerability arises because authorization was limited to write privileges on the Connector itself, not on the referenced resources. Apache NiFi installations that do not differentiate authorization levels across Connectors and Parameter Providers are not affected. The issue is addressed in Apache NiFi 2.12.0, which adds authorization checks for read access to Parameter Providers and verifies Asset ownership during configuration updates.
Potential Impact
An authenticated user with write privileges on a Connector but without read authorization on referenced Parameter Providers can apply Secret values from those Parameter Providers. This could lead to unauthorized use of Secrets in Connector configurations. Additionally, Assets can be referenced without verifying ownership, potentially allowing unauthorized Asset usage. The impact is limited by the requirement for authenticated users with write access to the Connector, and installations with uniform authorization across Connectors and Parameter Providers are not affected.
Mitigation Recommendations
Upgrade Apache NiFi to version 2.12.0 or later. This version enforces read access authorization on referenced Parameter Providers and verifies that referenced Assets belong to the Connector being configured during configuration update and verification. No other mitigation actions are specified or required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-08-27T17:28:06.599Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aaaf2ab55bf5e2cf514603a
Added to database: 09/16/2026, 19:48:59 UTC
Last enriched: 09/16/2026, 20:02:01 UTC
Last updated: 09/16/2026, 20:47:25 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.