CVE-2026-24014

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

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

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

Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process.

This issue affects Apache IoTDB: from 1.3.3 before 2.0.8.

Users are recommended to upgrade to version 2.0.8, which fixes the issue.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
40.3%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Jul 19, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-24014: Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write

http://www.openwall.com/lists/oss-security/2026/07/06/12

Vendor Advisories for CVE-2026-24014(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
apache-iotdb1.3.3 ... 2.0.6 (9 versions)2.0.8

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 84× 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 03:07 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 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 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 03:53 UTCGHSA enrichment
  13. 2026-07-16 23:56 UTCGHSA enrichment
  14. 2026-07-16 19:59 UTCGHSA enrichment
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 16:01 UTCGHSA enrichment
  18. 2026-07-16 12:02 UTCGHSA enrichment
  19. 2026-07-16 08:03 UTCGHSA enrichment
  20. 2026-07-16 04:06 UTCGHSA enrichment
  21. 2026-07-16 00:08 UTCGHSA enrichment
  22. 2026-07-15 20:11 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:14 UTCGHSA enrichment
Show 59 more
  1. 2026-07-15 12:18 UTCGHSA enrichment
  2. 2026-07-15 08:20 UTCGHSA enrichment
  3. 2026-07-15 04:22 UTCGHSA enrichment
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 00:17 UTCGHSA enrichment
  7. 2026-07-14 20:20 UTCGHSA enrichment
  8. 2026-07-14 16:23 UTCGHSA enrichment
  9. 2026-07-14 12:26 UTCGHSA enrichment
  10. 2026-07-14 08:29 UTCGHSA enrichment
  11. 2026-07-14 04:32 UTCGHSA enrichment
  12. 2026-07-14 00:35 UTCGHSA enrichment
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 20:38 UTCGHSA enrichment
  15. 2026-07-13 16:41 UTCGHSA enrichment
  16. 2026-07-13 12:44 UTCGHSA enrichment
  17. 2026-07-13 08:47 UTCGHSA enrichment
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 04:46 UTCGHSA enrichment
  21. 2026-07-13 00:48 UTCGHSA enrichment
  22. 2026-07-12 20:46 UTCGHSA enrichment
  23. 2026-07-12 16:45 UTCGHSA enrichment
  24. 2026-07-12 12:49 UTCGHSA enrichment
  25. 2026-07-12 08:52 UTCGHSA enrichment
  26. 2026-07-12 05:46 UTCEPSS rescore
  27. 2026-07-12 05:46 UTCEPSS rescore
  28. 2026-07-12 04:55 UTCGHSA enrichment
  29. 2026-07-12 00:58 UTCGHSA enrichment
  30. 2026-07-11 21:01 UTCGHSA enrichment
  31. 2026-07-11 17:04 UTCGHSA enrichment
  32. 2026-07-11 13:07 UTCGHSA enrichment
  33. 2026-07-11 09:10 UTCGHSA enrichment
  34. 2026-07-11 08:27 UTCEPSS rescore
  35. 2026-07-11 05:13 UTCGHSA enrichment
  36. 2026-07-11 01:16 UTCGHSA enrichment
  37. 2026-07-10 21:20 UTCGHSA enrichment
  38. 2026-07-10 17:23 UTCGHSA enrichment
  39. 2026-07-10 13:26 UTCGHSA enrichment
  40. 2026-07-10 09:29 UTCGHSA enrichment
  41. 2026-07-10 05:31 UTCGHSA enrichment
  42. 2026-07-10 01:34 UTCGHSA enrichment
  43. 2026-07-09 21:36 UTCGHSA enrichment
  44. 2026-07-09 19:10 UTCEPSS rescore
  45. 2026-07-09 17:40 UTCGHSA enrichment
  46. 2026-07-09 13:43 UTCGHSA enrichment
  47. 2026-07-09 09:46 UTCGHSA enrichment
  48. 2026-07-09 05:48 UTCGHSA enrichment
  49. 2026-07-09 01:51 UTCEG score recompute 9.80
  50. 2026-07-09 01:51 UTCGHSA enrichment
  51. 2026-07-08 15:15 UTCEPSS rescore
  52. 2026-07-08 15:15 UTCEPSS rescore
  53. 2026-07-07 13:46 UTCEPSS rescore
  54. 2026-07-06 19:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  55. 2026-07-06 16:27 UTCEPSS rescore
  56. 2026-07-06 16:27 UTCEPSS rescore
  57. 2026-07-06 09:42 UTCNVD update
  58. 2026-07-06 08:52 UTCEG score recompute
  59. 2026-07-06 08:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-24014?
CVE-2026-24014 is a critical vulnerability published on July 6, 2026. Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to…
When was CVE-2026-24014 disclosed?
CVE-2026-24014 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24014 actively exploited?
CVE-2026-24014 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-24014?
CVE-2026-24014 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-24014?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24014, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-24014

Explore →

Is Your Infrastructure Affected by CVE-2026-24014?

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