CVE-2026-40005

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

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

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

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

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache IoTDB. An attacker can write arbitrary files anywhere the IoTDB process has write permissions with unsafe API.

This issue affects Apache IoTDB: from 1.0.0 before 2.0.10.

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

CVSS v3
9.1
EG Score
9.1(high)
EPSS
27.0%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (2)

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

oss-security - CVE-2026-40005: Apache IoTDB: Path Traversal in Pipe File Transfer Receiver

http://www.openwall.com/lists/oss-security/2026/07/10/2

Vendor Advisories for CVE-2026-40005(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 48× in last 7d / 48× 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-16 01:05 UTCEG score recompute
  2. 2026-07-16 01:05 UTCGHSA enrichment
  3. 2026-07-15 21:16 UTCEG score recompute
  4. 2026-07-15 21:16 UTCGHSA enrichment
  5. 2026-07-15 17:28 UTCEG score recompute
  6. 2026-07-15 17:28 UTCGHSA enrichment
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 13:36 UTCEG score recompute
  10. 2026-07-15 13:35 UTCGHSA enrichment
  11. 2026-07-15 09:46 UTCEG score recompute
  12. 2026-07-15 09:46 UTCGHSA enrichment
  13. 2026-07-15 05:58 UTCEG score recompute
  14. 2026-07-15 05:57 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEG score recompute
  17. 2026-07-15 01:59 UTCGHSA enrichment
  18. 2026-07-14 22:11 UTCEG score recompute
  19. 2026-07-14 22:11 UTCGHSA enrichment
  20. 2026-07-14 18:20 UTCEG score recompute
  21. 2026-07-14 18:20 UTCGHSA enrichment
  22. 2026-07-14 14:31 UTCEG score recompute
  23. 2026-07-14 14:31 UTCGHSA enrichment
  24. 2026-07-14 10:41 UTCEG score recompute
  25. 2026-07-14 10:41 UTCGHSA enrichment
Show 23 more
  1. 2026-07-14 06:52 UTCEG score recompute
  2. 2026-07-14 06:52 UTCGHSA enrichment
  3. 2026-07-14 03:02 UTCEG score recompute
  4. 2026-07-14 03:02 UTCGHSA enrichment
  5. 2026-07-13 23:14 UTCEG score recompute
  6. 2026-07-13 23:14 UTCGHSA enrichment
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 19:26 UTCEG score recompute
  9. 2026-07-13 19:26 UTCGHSA enrichment
  10. 2026-07-13 15:38 UTCEG score recompute
  11. 2026-07-13 15:38 UTCGHSA enrichment
  12. 2026-07-13 11:49 UTCEG score recompute
  13. 2026-07-13 11:49 UTCGHSA enrichment
  14. 2026-07-13 08:01 UTCEG score recompute 9.10
  15. 2026-07-13 08:01 UTCGHSA enrichment
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-10 15:37 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  21. 2026-07-10 08:25 UTCNVD update
  22. 2026-07-10 07:49 UTCEG score recompute
  23. 2026-07-10 07:48 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-40005?
CVE-2026-40005 is a critical vulnerability published on July 10, 2026. Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache IoTDB. An attacker can write arbitrary files anywhere the IoTDB process has write permissions with unsafe API. This issue affects Apache IoTDB: from 1.0.0 before 2.0.10. Users are recommended to…
When was CVE-2026-40005 disclosed?
CVE-2026-40005 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40005 actively exploited?
CVE-2026-40005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40005?
CVE-2026-40005 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-40005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40005, 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-40005

Explore →

Is Your Infrastructure Affected by CVE-2026-40005?

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