Skip to main content
VulnerabilityPublished

CVE-2026-24014: Apache IoTDB · Improper Access Control

Affects Apache IoTDBSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.0.8 as a priority.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 53% 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:H/I:H/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 18 Nov 2026.

What to do

Upgrade Apache 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
  • =1.3.3
Fixed in–

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, which contains the fix for this vulnerability. There is no indication of alternative mitigations or temporary fixes. Restricting access to the internal DataNode RPC port to trusted networks can reduce exposure.

Description

Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process. 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…