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.
Published: 2026-07-06
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Apache IoTDB's DataNode by accepting an uploaded JAR file. The name supplied for the JAR is concatenated into a file path without proper validation, allowing an attacker to embed path-traversal sequences. This flaw lets the attacker write arbitrary files with the permissions of the IoTDB process, potentially compromising the system or installing malicious binaries. The weakness is a combination of improper access control and insecure file upload handling, represented by CWE-284 and CWE-434.

Affected Systems

The vulnerability affects Apache IoTDB DataNode components from version 1.3.3 up to, but not including, 2.0.8. The product is maintained by the Apache Software Foundation.

Risk and Exploitability

The CVSS score of 9.8 signifies a critical severity. The EPSS score indicates a very low probability of exploitation in the wild. The flaw is not listed in the CISA KEV catalog. The likely attack vector is an attacker who can reach description, it is inferred that the RPC interface accepts JAR uploads without requiring authentication or additional privileges. Exploitation therefore depends on network exposure of the RPC port and the ability to connect to it from an untrusted network.

Generated by OpenCVE AI on July 26, 2026 at 20:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache IoTDB to version 2.0.8 or later to apply the official patch.
  • Prevent exposure of the internal RPC port by configuring firewall rules or placing the DataNode behind a bastion host.
  • Run the IoTDB process with the least privilege necessary, ensuring it cannot write to critical system locations.

Generated by OpenCVE AI on July 26, 2026 at 20:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 06 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 06 Jul 2026 14:00:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache iotdb
Vendors & Products Apache
Apache iotdb

Mon, 06 Jul 2026 09:00:00 +0000

Type Values Removed Values Added
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.
Title Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write
Weaknesses CWE-284
CWE-434
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-07-06T20:37:58.998Z

Reserved: 2026-01-20T03:04:59.061Z

Link: CVE-2026-24014

cve-icon Vulnrichment

Updated: 2026-07-06T20:37:58.998Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-26T20:45:03Z

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-434

    Unrestricted Upload of File with Dangerous Type