CVE-2026-24014

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-06 09:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-25 15:10 UTC Last updatedMost recent change to the record

Details

Published

2026-07-06 09:16 UTC

Last modified

2026-10-25 15:10 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-284 · Improper access control

Record status

Analyzed

Affected

• Apache Iotdb < 2.0.8

Attack profile CVSS 3.1 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High