CVE-2026-40009

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Improper Privilege Management, Improper Access Control vulnerability in Apache IoTDB. Authenticated users can escalate to full tree-path access by renaming themselves to __internal_auditor.

This issue affects Apache IoTDB: from 2.0.8 before 2.0.10.

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

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-40009(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 49× 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-30 16:28 UTCEPSS rescore
  2. 2026-07-30 11:19 UTCEG score recompute
  3. 2026-07-30 11:19 UTCGHSA enrichment
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-29 11:44 UTCEG score recompute
  6. 2026-07-29 11:44 UTCGHSA enrichment
  7. 2026-07-28 12:12 UTCEG score recompute
  8. 2026-07-28 12:12 UTCGHSA enrichment
  9. 2026-07-27 14:13 UTCEPSS rescore
  10. 2026-07-27 11:44 UTCEG score recompute
  11. 2026-07-27 11:44 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 14:54 UTCEPSS rescore
  14. 2026-07-26 12:13 UTCEG score recompute
  15. 2026-07-26 12:13 UTCGHSA enrichment
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-24 14:17 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:10 UTCEG score recompute
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
Show 24 more
  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-19 02:29 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-17 01:30 UTCGHSA enrichment
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-16 01:59 UTCGHSA enrichment
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:27 UTCGHSA enrichment
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-14 02:56 UTCGHSA enrichment
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 03:24 UTCEG score recompute 6.50
  16. 2026-07-13 03:24 UTCGHSA enrichment
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-10 18:22 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  20. 2026-07-10 16:18 UTCNVD update
  21. 2026-07-10 15:37 UTCMITRE cvelistV5
  22. 2026-07-10 08:25 UTCNVD update
  23. 2026-07-10 07:49 UTCEG score recompute
  24. 2026-07-10 07:48 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-40009?
CVE-2026-40009 is a medium vulnerability published on July 10, 2026. Improper Privilege Management, Improper Access Control vulnerability in Apache IoTDB. Authenticated users can escalate to full tree-path access by renaming themselves to internal_auditor. This issue affects Apache IoTDB: from 2.0.8 before 2.0.10. Users are recommended to upgrade to version 2.0.10,…
When was CVE-2026-40009 disclosed?
CVE-2026-40009 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-40009 actively exploited?
CVE-2026-40009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.6% of all scored CVEs.
What is the CVSS score of CVE-2026-40009?
CVE-2026-40009 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-40009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40009, 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-40009

Explore →

Is Your Infrastructure Affected by CVE-2026-40009?

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