CVE-2026-81866

Apache NiFi: Missing Authorization for Assets and Secrets Referenced by Connector Configuration

Published Sep 16, 2026 CVSS 4.0 · 0.5 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Apache NiFi’s REST API for updating or verifying connector configurations fails to enforce read‑level authorization on referenced assets and secrets. An authenticated user with write privilege on a connector can supply references to any parameter provider or asset, causing the framework to store or apply secret values that the user would normally be barred from reading. The lack of ownership checks on assets allows an attacker to attach arbitrary assets to a connector without permission. This flaw permits non‑privileged users to gain access to protected secrets and asset data, potentially exposing sensitive configuration information.

Affected Systems

Apache NiFi versions 2.9.0 through 2.11.0 are affected. All installations without separate authorization levels for connectors and parameter providers are vulnerable. Upgrading beyond 2.11.0 removes the issue.

Risk and Exploitability

The CVSS score of 0.5 indicates a low‑impact vulnerability. The EPSS of less than 1% reflects a very low probability that exploitation will occur. Because the flaw requires an authenticated user with connector write rights, the practical exploitation window is narrow. The vulnerability is not currently listed in CISA’s KEV catalog. Still, an attacker may use the flaw to exfiltrate secrets from the system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache NiFi to version 2.12.0 or later, which validates read permissions for referenced parameter providers and verifies asset ownership during configuration updates.
  • If immediate upgrade is not possible, restrict connector write permissions to trusted administrators to limit the number of users that could apply unauthorized secrets.
  • Implement separate authorization boundaries for connectors and parameter providers so that write access to a connector does not imply read access to its referenced secrets.

Generated by OpenCVE AI on September 18, 2026 at 01:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:nifi:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Type Values Removed Values Added
First Time appeared Apache
Apache nifi
Vendors & Products Apache
Apache nifi
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Apache NiFi: Missing Authorization for Assets and Secrets Referenced by Connector Configuration
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 0.5, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:U/S:N/AU:Y/R:U/V:C/RE:L/U:Clear'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 17, 2026, 12:27 PM
Reserved
Aug 27, 2026, 5:28 PM
Status
Analyzed
Published
Sep 16, 2026, 8:17 PM
Modified
Sep 21, 2026, 1:38 PM