CVE-2026-44913

HIGHNVD 7.27.2
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory published 2026-06-22. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
31.1%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-44913: Apache NiFi: Improper Escaping of Table Names in CaptureChangeMySQL

http://www.openwall.com/lists/oss-security/2026/06/20/5

Vendor Advisories for CVE-2026-44913(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 79× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:15 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 03:09 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 14:20 UTCGHSA enrichment
  12. 2026-07-16 01:22 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 12:32 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 23:42 UTCGHSA enrichment
  17. 2026-07-14 10:52 UTCGHSA enrichment
  18. 2026-07-13 22:30 UTCEPSS rescore
  19. 2026-07-13 22:00 UTCGHSA enrichment
  20. 2026-07-13 09:11 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 20:21 UTCGHSA enrichment
  23. 2026-07-12 07:32 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 18:43 UTCGHSA enrichment
Show 60 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 05:54 UTCGHSA enrichment
  3. 2026-07-10 17:04 UTCGHSA enrichment
  4. 2026-07-10 04:09 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 15:17 UTCGHSA enrichment
  7. 2026-07-09 01:45 UTCGHSA enrichment
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 12:48 UTCGHSA enrichment
  10. 2026-07-07 23:56 UTCGHSA enrichment
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 11:08 UTCGHSA enrichment
  13. 2026-07-06 22:19 UTCGHSA enrichment
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 09:29 UTCGHSA enrichment
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 20:03 UTCGHSA enrichment
  18. 2026-07-05 07:13 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 18:24 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 05:33 UTCGHSA enrichment
  23. 2026-07-03 16:42 UTCGHSA enrichment
  24. 2026-07-03 03:51 UTCGHSA enrichment
  25. 2026-07-02 14:56 UTCGHSA enrichment
  26. 2026-07-02 02:08 UTCGHSA enrichment
  27. 2026-07-01 15:07 UTCEPSS rescore
  28. 2026-07-01 13:18 UTCGHSA enrichment
  29. 2026-07-01 00:29 UTCGHSA enrichment
  30. 2026-06-30 23:22 UTCEPSS rescore
  31. 2026-06-30 11:40 UTCGHSA enrichment
  32. 2026-06-29 22:46 UTCGHSA enrichment
  33. 2026-06-29 14:06 UTCEPSS rescore
  34. 2026-06-29 14:06 UTCEPSS rescore
  35. 2026-06-29 09:57 UTCGHSA enrichment
  36. 2026-06-28 21:08 UTCGHSA enrichment
  37. 2026-06-28 14:07 UTCEPSS rescore
  38. 2026-06-28 08:19 UTCGHSA enrichment
  39. 2026-06-28 04:56 UTCEPSS rescore
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-27 19:30 UTCGHSA enrichment
  42. 2026-06-27 06:41 UTCGHSA enrichment
  43. 2026-06-27 03:08 UTCEPSS rescore
  44. 2026-06-26 17:52 UTCGHSA enrichment
  45. 2026-06-26 05:02 UTCGHSA enrichment
  46. 2026-06-25 16:13 UTCGHSA enrichment
  47. 2026-06-25 13:49 UTCEPSS rescore
  48. 2026-06-25 13:49 UTCEPSS rescore
  49. 2026-06-25 03:23 UTCGHSA enrichment
  50. 2026-06-24 14:34 UTCEG score recompute 2.00
  51. 2026-06-24 14:34 UTCGHSA enrichment
  52. 2026-06-24 14:05 UTCEPSS rescore
  53. 2026-06-23 21:33 UTCEPSS rescore
  54. 2026-06-23 20:00 UTCNVD updateCVSS v3 → 7.2 · severity → HIGH
  55. 2026-06-23 16:13 UTCGHSA enrichment
  56. 2026-06-22 17:50 UTCEG score recompute 5.20
  57. 2026-06-22 17:50 UTCGHSA enrichment
  58. 2026-06-22 17:45 UTCNVD updateCVSS v3 → 5.2 · CVSS v4 → 5.2
  59. 2026-06-22 10:04 UTCEG score recompute
  60. 2026-06-22 10:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-44913?
CVE-2026-44913 is a high vulnerability published on June 22, 2026. 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…
When was CVE-2026-44913 disclosed?
CVE-2026-44913 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44913 actively exploited?
CVE-2026-44913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44913?
CVE-2026-44913 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-44913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44913, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-44913

Explore →

Is Your Infrastructure Affected by CVE-2026-44913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.