Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed DataNode internal RPC port
-
DeliveryInvoke Trigger-create RPC
-
ExploitSupply JAR name with ../ traversal
-
ExecutionWrite file outside Trigger directory
-
PersistOverwrite config/startup artifact
-
ImpactExecute code as IoTDB process
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The DataNode's internal RPC port (the inter-node Thrift interface, normally reachable only by other cluster nodes) must be exposed to a network the attacker can reach - this is the explicit precondition in the advisory and the primary limiting factor, since correctly segmented clusters keep this port internal-only. Given the CVSS vector's PR:N, no authentication is required once the port is reachable, and the attacker must be able to invoke the Trigger-creation RPC with a controlled JAR filename containing path-traversal sequences. Exploitation is limited to Apache IoTDB deployments running 1.3.3 through pre-2.0.8; impact and reach are bounded by the filesystem permissions of the IoTDB process account. |
| Impact | The signals conflict and must be weighed carefully. The vendor/NVD CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), which treats the flaw as remotely, trivially, and unauthenticatedly exploitable - but that scoring omits the description's explicit precondition that the internal DataNode RPC port must be exposed to an untrusted network, which is not the default deployment posture. That gating is echoed by the low EPSS probability (0.15%, 4th percentile), the absence of CISA KEV listing, and no known public POC, all of which argue this is a real-but-not-widespread priority rather than an imminent mass-exploitation event. In short: high theoretical impact (attacker-controlled file write, credibly escalatable to RCE) but exploitation depends on a misconfiguration/network-exposure condition, so real-world priority is elevated for internet-exposed or flat-network clusters and comparatively low for correctly segmented deployments. The CWE-284 classification versus the path-traversal mechanism is a minor inconsistency worth noting when triaging - treat it as an access-control failure that yields a path-traversal write primitive. |
| Exploit ScenarioDerived | An attacker with network reachability to an exposed DataNode internal RPC port sends a Trigger-creation request whose JAR filename contains '../' traversal sequences, causing IoTDB to write the attacker-supplied JAR (or arbitrary bytes) to a location outside the Trigger directory - for example over a configuration file, an executable, or a scheduled/startup artifact owned by the IoTDB process. By overwriting a file that IoTDB or the host later executes, the attacker can escalate the file-write primitive toward code execution as the IoTDB service account. No public POC is currently identified, and success depends on the internal RPC port being exposed to the attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Jul 06, 2026
Arbitrary file write in Apache IoTDB DataNode (versions 1.3.3 up to but not including 2.0.8) allows attackers who can reach the internal DataNode RPC port to smuggle path-traversal sequences in an uploaded Trigger JAR filename, writing files outside the Trigger installation directory with the IoTDB process's privileges. Because the write is attacker-controlled, it can plausibly be escalated to remote code execution by overwriting configuration or startup artifacts. There is no public exploit identified at time of analysis, and the EPSS score is low (0.15%, 4th percentile), consistent with exploitation being gated on an exposed internal port rather than a default-reachable service.
Earlier versions of this analysis (1)
Arbitrary file write in Apache IoTDB (versions 1.3.3 up to but not including 2.0.8) arises from the DataNode's internal RPC interface trusting an attacker-supplied Trigger JAR filename to construct a filesystem path without validation. If the internal DataNode RPC port is reachable from an untrusted network, an attacker can embed path-traversal sequences in the JAR name to write files anywhere the IoTDB process can write, plausibly escalating to code execution. This is Apache-reported with an available fix (2.0.8); there is no public exploit identified at time of analysis and it is not on CISA KEV.
RemediationAI
Vendor-released patch: upgrade Apache IoTDB to version 2.0.8, which fixes the insufficient JAR-name validation, per the Apache advisory (https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m). If immediate upgrade is not possible, the most effective compensating control is to ensure the internal DataNode RPC port is not reachable from untrusted networks: bind it to internal interfaces only and restrict it with firewall/security-group rules or network segmentation so only trusted ConfigNodes/DataNodes can connect - this directly removes the stated exploitation precondition, with the trade-off that misconfigured segmentation could disrupt legitimate cluster inter-node communication, so validate cluster membership after locking down. Additionally restrict who can create Trigger instances and monitor the Trigger installation directory for unexpected file writes; these are detective/limiting measures rather than a fix and do not substitute for upgrading to 2.0.8.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in pypi
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache IoTDB is an open-source time-series database purpose-built for IoT and industrial telemetry; it uses a distributed architecture in which ConfigNodes and DataNodes communicate over internal Thrift RPC interfaces. The affected code path is the DataNode internal RPC method that materializes user-defined Trigger plugins: the client-supplied Trigger JAR name is concatenated into a filesystem path used to persist the JAR into the Trigger installation directory without adequately sanitizing traversal metacharacters. NVD classifies the root cause as CWE-284 (Improper Access Control), reflecting that a privileged internal-only interface is being reached and trusted, though the concrete exploitation primitive is a classic path traversal (CWE-22) - the vendor tags corroborate both 'Path Traversal' and 'Authentication Bypass'. The single affected CPE is cpe:2.3:a:apache_software_foundation:apache_iotdb:*, i.e. the core IoTDB server product rather than a plugin or client library.
Know when Apache Iotdb gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AC:H because exploitation requires the non-default condition of the internal DataNode RPC port being network-exposed; PR:N since no auth is needed once reachable; C/I/A:H as attacker-controlled file write is credibly escalatable to RCE.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
4DescriptionCVE.org
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.
Articles & Coverage 1
Executive ViewAI
Apache IoTDB versions 1.3.3 through 2.0.7 contain a critical path-traversal vulnerability (CVSS 9.8) in the DataNode RPC port that enables arbitrary file write and potential remote code execution with IoTDB process privileges. The vulnerability requires attackers to access an internal RPC port-not exposed by default-significantly constraining real-world risk despite the critical severity rating.
Apply vendor patch (upgrade to version 2.0.8 or later). Until patching is complete: restrict DataNode RPC port network access to trusted internal systems only.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Apache Iotdb
View allMissing authentication for a critical function in Apache IoTDB 2.0.0 through 2.0.10 lets unauthenticated remote attacker
Unauthenticated remote attackers can bypass authentication in Apache IoTDB 2.0.0 through 2.0.10 through the Thrift RPC s
Unsafe reflection in Apache IoTDB's pipe processor lets a user-supplied fully qualified Java class name be loaded and in
Authentication bypass via capture-replay in Apache IoTDB (1.0.0 through 2.0.9) lets attackers reuse stale credentials ag
Arbitrary file write in Apache IoTDB (versions 1.0.0 through 2.0.9) lets remote attackers plant files anywhere the IoTDB
Apache IoTDB 2.0.0 through 2.0.11 mishandles identity in its Legacy Pipe receiver: the handshake and sendPipeData handle
Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the databa
Unauthenticated denial of service in Apache IoTDB (1.0.0 through 2.0.9) allows remote attackers to crash or degrade the
Denial of service in Apache IoTDB versions 1.3.3 through 2.0.7 lets remote attackers crash the DataNode process by submi
Authorization bypass in Apache IoTDB's REST API endpoint /rest/v2/fastLastQuery allows authenticated users to access las
Denial of service in Apache IoTDB versions 1.0.0 up to (but not including) 2.0.10 lets an unauthenticated network attack
Authentication bypass via sessionId spoofing in Apache IoTDB (1.3.3 through versions before 2.0.8) lets a remote, unauth
EUVD-2026-41854
GHSA-rpg4-r93p-w6gg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB