CVE-2026-24013

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-06. 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 — 3 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.

Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This allows authentication bypass and unauthorized reading of time-series data.

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.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
38.0%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (2)

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

oss-security - CVE-2026-24013: Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC

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

Vendor Advisories for CVE-2026-24013(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(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-24013?
CVE-2026-24013 is a critical vulnerability published on July 6, 2026. Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This…
When was CVE-2026-24013 disclosed?
CVE-2026-24013 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-24013 actively exploited?
CVE-2026-24013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-24013?
CVE-2026-24013 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-24013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24013, 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-24013

Explore →

Is Your Infrastructure Affected by CVE-2026-24013?

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