CVE-2026-86089: Apache NiFi: Missing Process Group Authorization for Connector Migration
Apache NiFi 2.11.0 Connector Migration REST APIs authorize only against the target Connector, skipping Process Group access checks (CVE-2026-86089, Low).
Missing Authorization in Apache NiFi Connector Migration Exposes Process Groups
CVE-2026-86089 is a missing-authorization flaw (CWE-862) in Apache NiFi 2.11.0's REST API for migrating version-controlled Process Groups into Connectors: the endpoints that list eligible migration sources and submit migration requests are authorized only against the target Connector, with no check of the source Process Group's access policies. An authenticated attacker with read access to a Connector can enumerate identifiers, names, and flow registry details of Process Groups outside their granted read policies, and with write access to the Connector can migrate such a Process Group, copying its flow definition, referenced assets, and component state into the Connector while leaving the source group disabled and renamed. Exposure is limited because migration excludes sensitive property values and requires the source Process Group to be stopped with empty queues, and installations that do not implement component-level Process Group authorization policies are not affected at all. No public proof-of-concept, CISA KEV listing, or known in-the-wild exploitation has been reported.
What to do: Upgrade to Apache NiFi 2.12.0, which filters migration sources to Process Groups the requesting user can read and requires write access to the source Process Group for migration requests. Until then, review which users hold read/write access to Connectors and check audit logs for unexpected migration API calls. Deployments that do not use component-level Process Group authorization policies are not affected.
| Product | Affected |
|---|---|
| Apache NiFi | 2.11.0 (fixed in 2.12.0) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Apache NiFi 2.11.0 supports migrating the contents of a version-controlled Process Group into a Connector using REST API methods that list eligible migration sources and submit migration requests. The framework authorized both methods against the target Connector alone, without evaluating access to the Process Groups involved. The absence of Process Group authorization allowed an authenticated user with read access to a Connector to enumerate the identifiers, names, and flow registry details of version-controlled Process Groups outside the scope of granted read policies. It also allowed a user with write access to a Connector to migrate a Process Group without write access to that Process Group, copying the flow definition, referenced assets, and component state into the Connector, and leaving the source Process Group disabled and renamed. Migration excludes sensitive property values and requires the source Process Group to be stopped with empty queues, which limits the scope of exposure. Apache NiFi installations that do not implement component-level authorization policies for Process Groups are not subject to this vulnerability, because the framework enforces Connector write permissions as the security boundary. Upgrading to Apache NiFi 2.12.0 is the recommended mitigation, which filters migration sources to Process Groups the requesting user is authorized to read, and requires write access to the source Process Group when submitting a migration request.
Apache NiFi 2.11.0 Connector Migration REST APIs authorize only against the target Connector, skipping Process Group access checks (CVE-2026-86089, Low).
Today 1.6K readers · 2.5K views · 779 reads · all time 189K views