Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Iotdb | >= 1.3.3, < 2.0.8 |
Related Weaknesses (CWE)
References
- https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3mMailing ListVendor Advisory
- http://www.openwall.com/lists/oss-security/2026/07/06/12Mailing ListThird Party Advisory
FAQ
What is CVE-2026-24014?
CVE-2026-24014 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 i...
How severe is CVE-2026-24014?
CVE-2026-24014 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-24014?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Iotdb.