Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-44913: Improper escaping of database table names in the CaptureChangeMySQL Processor included with Apache NiFi 1.2.0

43
This month
HIGH 7.2WATCHLISTUPGRADE

CVE-2026-44913 is a high-severity flaw (CVSS 7.2) affecting nifi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • High severity
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.6% (top 49%)
CISA exploited listNo
WeaknessCWE-116
Published2026-06-22
Last modified2026-10-25
Publisher (CNA): Apache Software Foundation · Vendor: apache

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache nifi UPGRADE
Affected: >= 1.2.0 and < 2.10.0
Fixed in: 2.10.0
Safe to downgrade to: a release before 1.2.0
1. Check installed version
apt-cache policy nifi || rpm -q nifi || nifi --version
2. UPGRADE to 2.10.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nifi
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nifi
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.2.0 (Debian / Ubuntu)
apt-cache madison nifi sudo apt install nifi=<VERSION_BEFORE_1.2.0> sudo apt-mark hold nifi
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nifi sudo dnf downgrade nifi-<VERSION_BEFORE_1.2.0> sudo dnf versionlock add nifi
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44913?

nifi: upgrade to 2.10.0. Exact commands for each OS are on this page.

Is CVE-2026-44913 being exploited?

CVE-2026-44913 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44913 affect?

CVE-2026-44913 affects nifi. Severity is high (CVSS 7.2). 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

How urgent is CVE-2026-44913?

Priority 43/100. High severity; On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.