dbcve.org
NifiApplication · Apache

CVE-2026-44913

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
Improper escaping of database table names in the CaptureChangeMySQL Processor included with Apache NiFi 1.2.0 through 2.9.0 allows for injecting SQL commands using crafted naming. Manual quoted boundaries added in Apache NiFi 1.8.0 narrowed the scope of potential injection options, but did not cover additional strategies. Apache NiFi installations that do not use the CaptureChangeMySQL Processor are not subject to this vulnerability. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, which incorporates more robust identifier escaping.

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

The CaptureChangeMySQL Processor in Apache NiFi 1.2.0 through 2.9.0 improperly escapes database table names, allowing SQL injection through crafted table name identifiers. A partial fix in version 1.8.0 added manual quoted boundaries but did not cover all injection strategies.

MitigationUpgrade Apache NiFi to version 2.10.0 which includes more robust identifier escaping. Systems not using the CaptureChangeMySQL Processor are unaffected.

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.2.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. Check installed Apache NiFi version
    Run 'nifi --version' or check the NiFi UI login page footer which displays the version. Also check the nifi-version.properties file in the NiFi installation directory.
    Affected if The installed version is 1.2.0 through 1.9.x or 2.0.0 through 2.9.x (anything < 2.10.0)
  2. Identify if CaptureChangeMySQL Processor is in use
    In NiFi UI, use the global search (Ctrl+F) or navigate through processor groups to locate any CaptureChangeMySQL processors. Alternatively, search flow XML configuration files for 'CaptureChangeMySQL' processor type.
    Affected if Any CaptureChangeMySQL Processor is present in the data flow, regardless of its configuration state
  3. Inspect CaptureChangeMySQL table name configuration
    Open each CaptureChangeMySQL Processor configuration (right-click > Configure > Properties) and examine the 'Table Name Pattern' property for user-supplied or dynamic table name values.
    Affected if The Table Name Pattern property contains wildcards, user variables, or values derived from external input that could be manipulated
  4. Review processor scheduling and state
    Check the 'Scheduling' tab in the processor configuration to see if the processor is scheduled to run, and examine the 'Status' tab for recent activity.
    Affected if The processor is actively scheduled and has recent run history, indicating active database interaction

A user is affected if their NiFi version is less than 2.10.0 AND they have deployed the CaptureChangeMySQL Processor in any active data flow with table name patterns that could be externally influenced.

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 Apache NiFi to version 2.10.0 which includes more robust identifier escaping. Systems not using the CaptureChangeMySQL Processor are unaffected.

Recommended fix High confidence

Apache NiFi 2.10.0

  1. Download Apache NiFi 2.10.0 from the official Apache NiFi releases page
  2. Follow the standard Apache NiFi upgrade procedure for your deployment method (binary or Docker)
  3. After upgrading, verify the CaptureChangeMySQL Processor configuration and test that database connectivity remains functional
  4. Review release notes for any configuration changes that may affect your existing dataflows

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

Fix this in Nifi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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