Missing Authorization Affecting apache-nifi package, versions <2.12.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-APACHENIFI-20047483
- published23 Sept 2026
- disclosed16 Sept 2026
Introduced: 16 Sep 2026
NewCVE-2026-82561 (opens in a new tab)How to fix?
Upgrade Minimos:latest apache-nifi to version 2.12.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache-nifi package and not the apache-nifi package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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
References
- https://www.cve.org/CVERecord?id=CVE-2026-82561
- https://github.com/advisories/GHSA-hfp7-cf28-6f6q
- https://osv.dev/vulnerability/MINI-76mw-rg95-q793
- https://osv.dev/vulnerability/CVE-2026-82561
- https://lists.apache.org/thread/opk7l8wqvnl85qxlzj3dnxp6qbk27lwm
- http://www.openwall.com/lists/oss-security/2026/09/16/9