Quick answers
- Is CVE-2026-24014 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24014 being exploited in the wild.
- How severe is CVE-2026-24014?
- Low severity, with a CVSS score of 3.1, published 6 July 2026.
- Which products and versions are affected?
- Apache Software Foundation IoTDB 1.3.3 to 2.0.7; apache-iotdb (PyPI) ECOSYSTEM:introduced=1.3.3,fixed=2.0.8.
- Is there a fix for CVE-2026-24014?
- Yes. apache-iotdb (PyPI): upgrade to 2.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24014 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-24014?
- Check whether you run Apache Software Foundation IoTDB or apache-iotdb (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- apache-iotdb (PyPI): upgrade to 2.0.8 or later
pip install "apache-iotdb>=2.0.8"
Technical details
A path traversal vulnerability exists in the Apache IoTDB DataNode's internal RPC interface. The root cause is insufficient validation of the Trigger JAR filename during the creation of Trigger instances, which is used to construct a local file path. If the internal DataNode RPC port is accessible over the network, an attacker can provide a filename containing traversal sequences (e.g., ../) to write arbitrary files outside the designated trigger directory. This exploit grants the attacker the ability to write files with the same privileges as the IoTDB process. The issue is resolved in version 2.0.8.
Affected products
- Apache IoTDB 1.3.3 to 2.0.7
Identifiers
- CVE-2026-24014
- PYSEC-2026-2081
Timeline
- 2026-07-06: disclosed
- 2026-07-06: advisory