CVE-2026-24014

criticalpriority · track · 0EPSS 0.007 · 53 %ileEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

0.69% (53rd) EPSS

CVSS 9.8 · critical

Is it mine?

3 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

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

Technical severity, 0–10. One row per scoring source.

9.8

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · ENISA EU

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondaryexploitability 3.9 · impact 5.9

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · OSV

v3.19criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: totalcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-284USCWE-434US

affected products (3)

Products and version ranges known to be affected.

Apache Software Foundation Apache IoTDB1.3.3 → 2.0.8enisa_euvdEU
apache iotdb1.3.3 → 2.0.8nvdUScpe:2.3:a:apache:iotdb:*:*:*:*:*:*:*:*
PyPI apache-iotdb1.3.3 → 2.0.8osvUSpkg:pypi/apache-iotdb

advisories (1)

Vendor and ecosystem advisories describing this.

PYSEC-2026-20812026-07-06vendor · osvUS
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.

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd nvd osv NVD CVE.org MITRE

published 2026-07-06modified 2026-10-25

references (5)

External citations — patches, advisories, analysis.

http://www.openwall.com/lists/oss-security/2026/07/06/12 cnnvd
https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m cnnvd
https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m enisa_euvd
http://www.openwall.com/lists/oss-security/2026/07/06/12Mailing ListThird Party Advisorynvd
https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3mMailing ListVendor Advisorynvd

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan