dbcve.org
NifiApplication · Apache

CVE-2026-44914

HIGH · 7.2 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 2.10.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache NiFi 1.12.0 through 2.9.0 lack proper authorization checks when replacing Process Groups containing components with the Restricted annotation. The framework failed to verify the restricted status of extension components during Process Group replacement, allowing users with general write access to add Restricted components that should require elevated privileges. This only affects deployments that have implemented specific authorization for Restricted components.

MitigationUpgrade to Apache NiFi 2.9.0 or later; note that this version removes the Restricted status authorization feature entirely, so alternative access controls may be needed if Restricted components were in use.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NifiApplication
Affected:>= 1.12.0, < 2.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed NiFi version
    Access the NiFi UI and navigate to the 'About' page (Help > About) or check the nifi.properties file for the 'nifi.version' property. Alternatively, check the classpath for the nifi-api JAR file version.
    Affected if The version is 1.12.0 through 2.9.0 inclusive
  2. Verify if Restricted component authorization is configured
    Review the NiFi authorizer configuration (authorizers.xml) to determine if any policies exist for 'Restricted' components. Check the 'accessPolicy.xml' or equivalent policy storage for component-level restrictions marked as restricted.
    Affected if Policies specifically targeting Restricted components have been defined in the authorization framework
  3. Confirm Process Group replacement capability is accessible
    Check if users have write access to any Process Group and have access to the 'Replace' or 'Import' Process Group functionality in the UI. Verify if template import or Process Group substitution features are enabled.
    Affected if Users with general write access to Process Groups can perform replacement or import operations, and restricted component policies would be bypassed during such operations

You are affected if your NiFi version is between 1.12.0 and 2.9.0 AND you have implemented authorization policies for Restricted components that could be bypassed via Process Group replacement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.0 or later
Fixed in 2.10.0
Interim mitigation

Upgrade to Apache NiFi 2.9.0 or later; note that this version removes the Restricted status authorization feature entirely, so alternative access controls may be needed if Restricted components were in use.

Recommended fix High confidence

Apache NiFi 2.10.0 or later

  1. 1. Backup your current Apache NiFi configuration and data directories before proceeding with any upgrade.
  2. 2. Review the Apache NiFi release notes for versions 2.10.0 and later to understand changes and potential migration requirements.
  3. 3. Download Apache NiFi 2.10.0 or later from the official Apache NiFi releases page (https://nifi.apache.org/download/).
  4. 4. Stop the running NiFi service cleanly to avoid data corruption.
  5. 5. Install the new NiFi version following the standard upgrade procedure in the Apache NiFi Administration Guide.
  6. 6. Verify that authorization policies are properly configured, especially if you use custom implementations for Restricted component authorization.
  7. 7. Start NiFi and validate that the application functions correctly with the new version.
  8. 8. Test that users with general write access can no longer add components with Restricted status without proper elevated permissions.
Caveat Review release notes for changes between your current version and 2.10.0+; note that the fix removes framework enforcement of Restricted status, so custom authorization implementations may be needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nifi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44914 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data