Skip to main content
VulnerabilityPublished

CVE-2026-24012: Apache IoTDB · Uncontrolled Resource Consumption

Affects Apache IoTDBSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.0.8 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade Apache IoTDB and org.apache.iotdb/iotdb to 2.0.8.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache IoTDBAffected
  • >=1.3.3 <2.0.8
Fixed in
  • 2.0.8
Mavenorg.apache.iotdb/iotdbpkg:maven/org.apache.iotdb/iotdbOther threatsAffected
  • <2.0.8
Fixed in
  • 2.0.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache IoTDB to version 2.0.8 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is specified. Patch status is confirmed by the vendor advisory recommending upgrade to 2.0.8.

Description

Uncontrolled Resource Consumption vulnerability in Apache IoTDB. Some interface fails to impose reasonable limits on the time span and aggregation interval of the query. An attacker can construct a request with extreme parameters (e.g., a very large time range combined with a minimal interval). This forces the DataNode to build an enormous result set in memory, which exhausts the Java heap and causes the DataNode process to crash. 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.

References

Community reviews

Loading reviews…