Severity:
Affected versions:
- Apache NiFi (org.apache.nifi:nifi-web-api) 1.12.0 through 2.9.0
Description:
Apache NiFi 1.12.0 through 2.9.0 are missing authorization when replacing Process Groups that include extension components with specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required, but framework authorization did not check restricted status when handling requests to replace Process Groups. The missing authorization permits a user with general write access to add components with Restricted status. Apache NiFi installations that do not implement specific authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.9.0 is the recommended mitigation, which removes the implementation of Restricted status authorization from the framework.
This issue is being tracked as NIFI-15845
Credit:
Roberto Suggi Liverani from NATO Cyber Security Centre (NCSC) (finder)
References:
https://nifi.apache.org/ https://www.cve.org/CVERecord?id=CVE-2026-44914 https://issues.apache.org/jira/browse/NIFI-15845
Timeline:
2026-04-27: reported
Severity:
Affected versions:
- Apache NiFi (org.apache.nifi:nifi-web-api) 1.1.0 before 2.8.0
Description:
Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization did not check restricted status when updating a component previously added. The missing authorization requires a more privileged user to add a restricted component to the flow configuration, but permits a less privileged user to make property configuration changes. Apache NiFi installations that do not implement different levels of authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.8.0 is the recommended mitigation.
This issue is being tracked as NIFI-15567
Credit:
David Handermann (finder)
References:
https://nifi.apache.org/ https://www.cve.org/CVERecord?id=CVE-2026-25903 https://issues.apache.org/jira/browse/NIFI-15567
Timeline:
2026-02-06: reported