CVE-2026-24014

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 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(medium)
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 PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Aug 23, 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 44× in last 7d / 219× 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.

Showing the most recent 100 of 323 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-26 13:56 UTCGHSA enrichment
  3. 2026-08-25 16:02 UTCEG score recompute
  4. 2026-08-25 16:02 UTCGHSA enrichment
  5. 2026-08-25 13:48 UTCEPSS rescore
  6. 2026-08-25 12:02 UTCGHSA enrichment
  7. 2026-08-25 04:43 UTCGHSA enrichment
  8. 2026-08-25 00:46 UTCGHSA enrichment
  9. 2026-08-24 20:49 UTCEG score recompute
  10. 2026-08-24 20:49 UTCGHSA enrichment
  11. 2026-08-24 14:00 UTCGHSA enrichment
  12. 2026-08-24 10:03 UTCEG score recompute
  13. 2026-08-24 10:03 UTCGHSA enrichment
  14. 2026-08-24 04:06 UTCGHSA enrichment
  15. 2026-08-23 21:46 UTCGHSA enrichment
  16. 2026-08-23 17:49 UTCGHSA enrichment
  17. 2026-08-23 13:53 UTCGHSA enrichment
  18. 2026-08-23 09:56 UTCGHSA enrichment
  19. 2026-08-23 05:59 UTCGHSA enrichment
  20. 2026-08-23 01:59 UTCEG score recompute
  21. 2026-08-23 01:59 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 22:01 UTCGHSA enrichment
  24. 2026-08-22 18:04 UTCGHSA enrichment
  25. 2026-08-22 13:01 UTCGHSA enrichment
Show 75 more
  1. 2026-08-22 08:57 UTCGHSA enrichment
  2. 2026-08-22 04:59 UTCGHSA enrichment
  3. 2026-08-22 00:58 UTCEG score recompute
  4. 2026-08-22 00:58 UTCGHSA enrichment
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 21:01 UTCGHSA enrichment
  7. 2026-08-21 17:04 UTCGHSA enrichment
  8. 2026-08-21 12:12 UTCGHSA enrichment
  9. 2026-08-21 08:15 UTCGHSA enrichment
  10. 2026-08-21 04:18 UTCGHSA enrichment
  11. 2026-08-20 23:43 UTCEG score recompute
  12. 2026-08-20 23:43 UTCGHSA enrichment
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 19:46 UTCGHSA enrichment
  15. 2026-08-20 15:49 UTCGHSA enrichment
  16. 2026-08-20 10:28 UTCGHSA enrichment
  17. 2026-08-20 06:31 UTCGHSA enrichment
  18. 2026-08-20 02:34 UTCEG score recompute
  19. 2026-08-20 02:33 UTCGHSA enrichment
  20. 2026-08-19 17:03 UTCEPSS rescore
  21. 2026-08-19 13:14 UTCGHSA enrichment
  22. 2026-08-19 09:18 UTCGHSA enrichment
  23. 2026-08-19 04:52 UTCGHSA enrichment
  24. 2026-08-19 00:55 UTCGHSA enrichment
  25. 2026-08-18 20:49 UTCEG score recompute
  26. 2026-08-18 20:49 UTCGHSA enrichment
  27. 2026-08-18 13:48 UTCEPSS rescore
  28. 2026-08-18 11:00 UTCGHSA enrichment
  29. 2026-08-18 03:50 UTCGHSA enrichment
  30. 2026-08-17 22:42 UTCGHSA enrichment
  31. 2026-08-17 14:00 UTCEG score recompute
  32. 2026-08-17 14:00 UTCGHSA enrichment
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 10:03 UTCGHSA enrichment
  35. 2026-08-17 06:06 UTCGHSA enrichment
  36. 2026-08-17 01:18 UTCGHSA enrichment
  37. 2026-08-16 21:21 UTCGHSA enrichment
  38. 2026-08-16 17:24 UTCEG score recompute
  39. 2026-08-16 17:24 UTCGHSA enrichment
  40. 2026-08-16 14:56 UTCEPSS rescore
  41. 2026-08-16 13:21 UTCGHSA enrichment
  42. 2026-08-16 09:24 UTCGHSA enrichment
  43. 2026-08-16 05:27 UTCEG score recompute
  44. 2026-08-16 05:27 UTCGHSA enrichment
  45. 2026-08-16 02:14 UTCEPSS rescore
  46. 2026-08-16 01:31 UTCGHSA enrichment
  47. 2026-08-15 21:34 UTCGHSA enrichment
  48. 2026-08-15 17:37 UTCGHSA enrichment
  49. 2026-08-15 13:40 UTCGHSA enrichment
  50. 2026-08-15 09:37 UTCGHSA enrichment
  51. 2026-08-15 05:40 UTCGHSA enrichment
  52. 2026-08-15 01:43 UTCEG score recompute
  53. 2026-08-15 01:43 UTCGHSA enrichment
  54. 2026-08-15 01:30 UTCEPSS rescore
  55. 2026-08-14 21:46 UTCGHSA enrichment
  56. 2026-08-14 17:50 UTCGHSA enrichment
  57. 2026-08-14 13:47 UTCGHSA enrichment
  58. 2026-08-14 09:51 UTCGHSA enrichment
  59. 2026-08-14 05:54 UTCGHSA enrichment
  60. 2026-08-14 01:57 UTCGHSA enrichment
  61. 2026-08-13 22:00 UTCEG score recompute
  62. 2026-08-13 22:00 UTCGHSA enrichment
  63. 2026-08-13 22:00 UTCEPSS rescore
  64. 2026-08-13 18:03 UTCGHSA enrichment
  65. 2026-08-13 13:49 UTCGHSA enrichment
  66. 2026-08-13 09:52 UTCGHSA enrichment
  67. 2026-08-13 05:56 UTCGHSA enrichment
  68. 2026-08-13 01:59 UTCGHSA enrichment
  69. 2026-08-12 22:03 UTCGHSA enrichment
  70. 2026-08-12 18:06 UTCGHSA enrichment
  71. 2026-08-12 14:09 UTCEG score recompute
  72. 2026-08-12 14:09 UTCGHSA enrichment
  73. 2026-08-12 13:50 UTCEPSS rescore
  74. 2026-08-12 10:12 UTCGHSA enrichment
  75. 2026-08-12 06:15 UTCGHSA enrichment

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 1% probability of exploitation in the next 30 days, which ranks it in the top 49.8% of all scored CVEs.
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.