CVE-2026-81866: Apache NiFi: Missing Authorization for Assets and Secrets Referenced by Connector Configuration
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache NiFito a version that resolves this vulnerability.Fixed in 2.12.0Patch CVE-2026-81866
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments are affected when they use different authorization levels for Connectors and Parameter Providers. Installations that do not differentiate authorization across those resources are not subject to this vulnerability, because Connector write permission remains the security boundary.
What access does an attacker need?
An attacker must be an authenticated user with permission to modify a Connector. They can exploit the issue if they lack permission to read a referenced Parameter Provider but can submit that provider's Secret references in a Connector configuration update or verification request.
Can an attacker reference Assets from another Connector?
Yes. The affected API methods accepted Asset identifiers without confirming that the Asset belonged to the Connector being configured.
What is the recommended remediation?
Upgrade to Apache NiFi 2.12.0. This version checks read authorization for referenced Parameter Providers and verifies ownership of referenced Assets during Connector configuration updates and verification.