CVE-2026-68979: Apache NiFi: Missing Authorization for Components Referenced by Parameter Context Updates
Apache NiFi 1.10.0 through 2.10.0 provides a Parameter Context update REST API method that does not enforce authorization checking on components referencing Parameter values. An authenticated user authorized to modify a Parameter Context but not authorized on referencing components can alter Parameter values affecting those components. In deployments where a Parameter value contains executable scripting content, updating a Parameter can result in code execution during automatic component validation without starting the referencing component. The impact is limited to stopped components by existing verification checks, and the issue applies only to deployments using component-level authorization policies. Fixed in Apache NiFi 2.11.0 by aligning the Parameter Context update method authorization with other methods, adding authorization checking on affected components.
Research notes
- Root causeThe Parameter Context update REST API method in Apache NiFi enforced authorization only on the Parameter Context itself (read/write privileges) but did not check whether the authenticated user was authorized on components that reference the Parameter values. This allowed a user with Parameter Context modification rights to alter values affecting components they were not authorized to access.
- Technical detailWhen a Parameter value contains executable scripting content, updating the Parameter triggers code execution during automatic component validation, even without starting the referencing component. The impact is limited to stopped components by existing verification checks and to deployments using component-level authorization policies.
- MitigationFixed in Apache NiFi 2.11.0 by adding authorization checking on affected components during Parameter Context updates, aligning the method with other authorization patterns.