CVE-2026-82561

Apache NiFi: Missing Authorization for Components Referenced in Flow Update Methods

Published Sep 16, 2026 CVSS 4.0 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
Apache NiFi 1.5.0 through 2.11.0 provide REST API methods that replace the entire contents of a Process Group using a client-supplied flow definition, covering Process Group flow replacement together with versioned flow update and rebase operations. Framework authorization for these methods was limited to read and write privileges on the Process Group itself, unlike the corresponding asynchronous update request methods, which also authorize the components encapsulated in the Process Group along with referenced Controller Services, Parameter Contexts, and Parameter Providers. As a result of the missing authorization, an authenticated user with write access to a Process Group could supply a flow definition that modifies or removes components in descendant Process Groups protected by more restrictive access policies, and could bind components to Controller Services and Parameter Contexts without authorization for those referenced components. Existing verification checks limited the impact to stopped components, and the issue applies only to deployments that use component-level authorization policies, because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which applies consistent reference resolution and component authorization across Process Group replacement and versioned flow update methods

Analysis

AI-generated

Technical impact

The vulnerability arises from missing authorization checks when replacing the contents of a Process Group via the REST API. This flaw, based on CWE‑862, permits an authenticated user who has write permission on a Process Group to upload a new flow definition that modifies or removes components in nested Process Groups guarded by stricter access policies, or to bind components to Controller Services and Parameter Contexts without the proper authorizations. As a result, the attacker can introduce unauthorized configuration changes that may disrupt services or expose sensitive interactions. Existing verification checks limit the impact to stopped components, but the potential for configuration manipulation remains significant.

Affected Systems

Apache NiFi versions 1.5.0 through 2.11.0 are affected by this issue. The flaw is only present in deployments that enable component‑level authorization policies; systems that rely solely on Process Group level permissions are not impacted. The recommended fix is to upgrade to NiFi 2.12.0 or later, which enforces consistent reference resolution and component authorization for all flow update methods.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity, and the EPSS score of less than 1% suggests a low probability of exploitation. The vulnerability is not listed in CISA's KEV catalog. An attacker would need to be authenticated with write access to a Process Group, a scenario that typically indicates internal or compromised credentials. Given the limited exploitation window and the requirement for existing component‑level security, the overall risk is moderate but still actionable.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache NiFi to version 2.12.0 or newer to apply consistent authorization checks across all flow update methods.
  • If an upgrade cannot be performed immediately, tighten role‑based access controls by removing write and update permissions from Process Groups that contain sensitive child components, ensuring only trusted administrators can perform flow replacements.
  • Consider restricting access to the flow update API endpoint to trusted hosts or networks, and enable audit logging to monitor for anomalous flow replacement activity.

Generated by OpenCVE AI on September 18, 2026 at 01:36 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:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Apache
Apache nifi
Vendors & Products Apache
Apache nifi
Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

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

Type Values Removed Values Added
Description Apache NiFi 1.5.0 through 2.11.0 provide REST API methods that replace the entire contents of a Process Group using a client-supplied flow definition, covering Process Group flow replacement together with versioned flow update and rebase operations. Framework authorization for these methods was limited to read and write privileges on the Process Group itself, unlike the corresponding asynchronous update request methods, which also authorize the components encapsulated in the Process Group along with referenced Controller Services, Parameter Contexts, and Parameter Providers. As a result of the missing authorization, an authenticated user with write access to a Process Group could supply a flow definition that modifies or removes components in descendant Process Groups protected by more restrictive access policies, and could bind components to Controller Services and Parameter Contexts without authorization for those referenced components. Existing verification checks limited the impact to stopped components, and the issue applies only to deployments that use component-level authorization policies, because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which applies consistent reference resolution and component authorization across Process Group replacement and versioned flow update methods
Title Apache NiFi: Missing Authorization for Components Referenced in Flow Update Methods
Weaknesses CWE-862
References
Metrics cvssV4_0

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

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 17, 2026, 7:12 PM
Reserved
Aug 29, 2026, 11:44 PM
Status
Analyzed
Published
Sep 16, 2026, 8:17 PM
Modified
Sep 21, 2026, 1:54 PM