CVE-2026-40007

HIGHPre-NVD 7.5Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

Uncontrolled Recursion, Uncontrolled Resource Consumption vulnerability in Apache IoTDB. When pipe_air_gap_receiver_enabled=true, the IoTDB AirGap receiver's readLength method calls itself recursively each time it recognises the E-language prefix in socket data, with no depth limit. An unauthenticated attacker can send a stream of repeated E-language prefixes that drives the recursion arbitrarily deep, exhausting the receiver thread's JVM stack and raising StackOverflowError.

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
7.5
EG Score
0.0(none)
EPSS
19.7%
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-40007: Apache IoTDB: Unauthenticated unbounded recursion in IoTDB AirGap receiver's E-language prefix parser causes per-connection StackOverflowError

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

Vendor Advisories for CVE-2026-40007(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 6× in last 7d / 6× 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-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-10 14:42 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  4. 2026-07-10 08:25 UTCNVD update
  5. 2026-07-10 07:49 UTCEG score recompute
  6. 2026-07-10 07:48 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-40007?
CVE-2026-40007 is a high vulnerability published on July 10, 2026. Uncontrolled Recursion, Uncontrolled Resource Consumption vulnerability in Apache IoTDB. When pipeairgapreceiverenabled=true, the IoTDB AirGap receiver's readLength method calls itself recursively each time it recognises the E-language prefix in socket data, with no depth limit. An unauthenticated…
When was CVE-2026-40007 disclosed?
CVE-2026-40007 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-40007 actively exploited?
CVE-2026-40007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40007?
CVE-2026-40007 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.
How do I remediate CVE-2026-40007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40007, 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-40007

Explore →

Is Your Infrastructure Affected by CVE-2026-40007?

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