Skip to main content
VulnerabilityPublished Updated

CVE-2026-24015: Apache IoTDB · Binding to an Unrestricted IP Address

Affects Apache IoTDBSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.0.7 or 1.3.7 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.7, 1.3.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Mar 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 30 Oct 2026.

What to do

Upgrade Apache IoTDB and org.apache.iotdb/iotdb to 2.0.7 or 1.3.7.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache IoTDBAffected
  • >=2.0.0 <2.0.7
Fixed in
  • 2.0.7
Apache Software FoundationApache IoTDBAffected
  • >=1.0.0 <1.3.7
Fixed in
  • 1.3.7
Mavenorg.apache.iotdb/iotdbpkg:maven/org.apache.iotdb/iotdbOther threatsAffected
  • =1.0.0 <1.3.7
  • >=2.0.0 <2.0.7
Fixed in
  • 1.3.7
  • 2.0.7

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

AI-suggested

To mitigate CVE-2026-24015, organizations should immediately upgrade Apache IoTDB to versions 1.3.7 or 2.0.7, where the vulnerability is fixed. Beyond patching, administrators should review and restrict network bindings to limit exposure only to trusted IP addresses or internal networks. Implement network segmentation and firewall rules to control access to IoTDB services, preventing unauthorized external connections. Enable and enforce authentication and encryption mechanisms where possible to protect data in transit and access control. Regularly audit IoTDB configurations and monitor network traffic for unusual access patterns. Employ intrusion detection systems (IDS) and endpoint security solutions to detect and respond to potential exploitation attempts. Finally, maintain an up-to-date inventory of IoTDB deployments and ensure timely application of security updates as part of a robust vulnerability management program.

Description

A vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 1.3.7, from 2.0.0 before 2.0.7. Users are recommended to upgrade to version 1.3.7 or 2.0.7, which fixes the issue.

References

Community reviews

Loading reviews…