dbcve.org
NifiApplication · Apache

CVE-2026-44911

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 2.10.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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
Authorization handling for component configuration verification requests in Apache NiFi 1.15.0 through 2.9.0 allows clients with read access to submit proposed configuration properties. The proposed properties override current configuration, enabling users with read access to invoke predefined verification methods with alternative settings. Apache NiFi installations that do not implement different levels of authorization for viewing and modifying component configuration are not subject to this vulnerability. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, requiring write access to submit configuration verification requests.

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.15.0 through 2.9.0 contains an authorization bypass where users with only read access can submit configuration verification requests that override current component settings. This allows read-only users to invoke predefined verification methods with alternative configuration properties, effectively bypassing write authorization requirements.

MitigationUpgrade to Apache NiFi 2.10.0 or later, which enforces proper write-access authorization for configuration verification requests.

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.15.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Determine installed NiFi version
    Check the NiFi version by accessing the NiFi API endpoint /nifi-api/flow/about or checking the nifi-version.properties file in the NiFi installation directory
    Affected if The installed version is 1.15.0 through 2.9.0 (inclusive)
  2. Identify read-only users
    Review user/tenant configurations in NiFi's authorizer configuration. Access the Users tab in NiFi UI or query the authorizer via /nifi-api/access/tenants/users to list all users and their granted permissions
    Affected if Any user account exists with only READ access to resources (no WRITE or DELETE permissions)
  3. Verify configuration verification endpoint accessibility
    Attempt to access or invoke the configuration verification API endpoint (typically /nifi-api/controller/config/verification-requests or similar) using a read-only user's credentials
    Affected if A read-only user can successfully submit configuration verification requests that override component settings
  4. Review authorization policies for verification methods
    Examine the NiFi policy configurations at /nifi-api/access/policies or through the NiFi UI Policies tab. Check if any policies grant read-only users access to invoke verification methods with alternative properties
    Affected if Policies exist that allow read-only users to trigger verification operations that modify configuration

You are affected if NiFi version is between 1.15.0 and 2.9.0 inclusive AND your system contains users with only read access who can access configuration verification functionality.

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.10.0 or later, which enforces proper write-access authorization for configuration verification requests.

Recommended fix High confidence

Apache NiFi 2.10.0

  1. 1. Review the Apache NiFi 2.10.0 release notes and upgrade guide for any migration requirements
  2. 2. Create a backup of the current NiFi configuration and flow definition
  3. 3. Stop the NiFi service
  4. 4. Upgrade the NiFi installation to version 2.10.0
  5. 5. Verify that the upgrade completed successfully
  6. 6. Confirm that the authorization fix is working by testing that read-only users can no longer submit configuration verification requests with alternative properties
  7. 7. Restart the NiFi service

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

Fix this in Nifi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44911 — 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-44911 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