Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach IoTDB pipe interface
-
DeliverySubmit pipe with malicious class name
-
ExploitServer calls Class.forName().newInstance()
-
ExecutionConstructor/static initializer runs in JVM
-
ImpactCode execution as IoTDB process
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V15 - Secure Coding and Architecture Reflection safety, class allowlisting
|
| Exploitation Conditions | Exploitation requires the ability to configure a pipe processor in Apache IoTDB - specifically supplying a fully qualified Java class name that the pipe subsystem loads via Class.forName().newInstance(). The target class must be present on the IoTDB server classpath for instantiation to succeed, and the pipe/stream-sync feature must be in use. The published CVSS marks PR:N (no privileges), but defining or altering a pipe is normally an authenticated administrative operation, which is the primary limiting factor; realistic exploitation therefore hinges on whether pipe management is exposed to unauthenticated or low-privilege users in a given deployment. Affected only on versions 1.0.0 through 2.0.9. |
| Impact | The signals conflict and should be weighed rather than taken at face value. The published CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N, total CIA impact) implies unauthenticated network-reachable RCE, but the described trigger - configuring a pipe processor with a class name - is a privileged administrative/SQL operation in IoTDB, so PR:N appears optimistic; in practice an attacker likely needs authenticated access to define or alter a pipe, which materially lowers real-world exposure. CISA SSVC aligns partially: Technical Impact 'total' and Automatable 'yes' support high severity if reachable, but Exploitation is rated 'none' and EPSS is only 0.25% (17th percentile), and there is no KEV listing and no known POC. Net assessment: a genuinely serious code-execution primitive, but its realistic priority is moderated by the probable authentication requirement and the absence of observed exploitation - patch promptly, but this is not evidence of mass, unauthenticated, internet-wide compromise. Verify with the vendor whether pipe-processor creation is reachable without authentication before treating it as a PR:N issue. |
| Exploit ScenarioDerived | An attacker with the ability to define or modify a pipe in IoTDB creates a pipe whose processor is set to an attacker-chosen fully qualified class name; when IoTDB instantiates it via Class.forName().newInstance(), the class's constructor or static initializer runs inside the database JVM, giving code execution with the server's privileges. Because the flaw is low-complexity and the input is directly reflected, exploitation is reliable once the pipe-configuration path is reachable, though no public POC is currently known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Jul 10, 2026
Unsafe reflection in Apache IoTDB's pipe processor lets a user-supplied fully qualified Java class name be loaded and instantiated via Class.forName().newInstance() with no allowlisting, enabling arbitrary class loading and likely remote code execution in the database server process. It affects all releases from 1.0.0 up to (but not including) 2.0.10 and is fixed in 2.0.10. No public exploit identified at time of analysis, and EPSS is low (0.25%, 17th percentile), though CISA SSVC rates the technical impact as total and considers exploitation automatable.
Earlier versions of this analysis (2)
Unsafe reflection in Apache IoTDB's pipe processor lets remote attackers achieve arbitrary code execution by supplying an externally-controlled, fully-qualified Java class name that is loaded via Class.forName().newInstance() with no validation or allowlisting. All releases from 1.0.0 up to (but not including) 2.0.10 are affected, and the vendor-assigned CVSS of 9.8 reflects full compromise of confidentiality, integrity, and availability. Currently there is no public exploit identified at time of analysis and EPSS is low (0.25%), but the CISA SSVC assessment rates the flaw as fully automatable with total technical impact.
Unsafe reflection in the Apache IoTDB pipe processor (versions 1.0.0 through 2.0.9) lets a user who can define a pipe supply an arbitrary fully-qualified Java class name that the server loads and instantiates via Class.forName().newInstance() with no allowlist or validation. This enables loading of unintended classes whose constructors execute server-side, tagged by the reporter as an information-disclosure risk but carrying potential for broader code execution depending on available classes. No public exploit identified at time of analysis and the flaw is not on CISA KEV; it is fixed in IoTDB 2.0.10.
RemediationAI
Vendor-released patch: 2.0.10 - upgrade Apache IoTDB to 2.0.10, which adds validation/allowlisting to the pipe processor class loading, per the Apache advisory (https://lists.apache.org/thread/fm8cpvzbox2qqy99ztglm8wkk1nrg9ng). If immediate upgrade is not possible, restrict who can create or alter pipes by tightening IoTDB authentication and authorization so that only trusted administrators hold pipe-management privileges, and avoid exposing the IoTDB service ports to untrusted networks (place them behind a firewall or restrict to a management VLAN); the trade-off is reduced convenience for legitimate data-sync automation and no protection against an already-privileged malicious insider. Monitor pipe definitions for unexpected or non-standard processor class names as a detective control until patched.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
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 aimed at IoT and industrial telemetry workloads, running on the JVM. The affected component is the pipe subsystem, IoTDB's stream-processing/data-synchronization feature, where a pipe can be configured with a custom 'processor' plugin identified by class name. The root cause is CWE-470 (Use of Externally-Controlled Input to Select Classes or Code, 'Unsafe Reflection'): the processor name is passed directly to reflective instantiation (Class.forName(name).newInstance()) without validation, type-checking against an expected interface, or an allowlist of permitted classes. This lets an attacker who controls that input coerce the JVM into loading and constructing arbitrary classes present on the classpath, whose constructors or static initializers can execute attacker-influenced logic. The single CPE cpe:2.3:a:apache_software_foundation:apache_iotdb:*:*:*:*:*:*:*:* confirms the product scope without version bounding in the CPE string itself.
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
Network-reachable and low-complexity, but defining a pipe processor is an authenticated operation so PR:L; unsafe reflection yields code execution with full CIA impact.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
5DescriptionCVE.org
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Apache IoTDB. The pipe processor reads a fully qualified Java class name and instantiates it using Class.forName().newInstance() without any validation or allowlisting.
This issue affects Apache IoTDB: from 1.0.0 before 2.0.10.
Users are recommended to upgrade to version 2.0.10, which fixes the issue.
Articles & Coverage 3
Executive ViewAI
Apache IoTDB versions 1.0.0-2.0.9 contain a critical remote code execution vulnerability in the pipe processor that enables arbitrary Java class instantiation, potentially allowing attackers to execute code within the database server. This threatens organizations running affected versions with direct database compromise and data theft. Vendor-released patch version 2.0.10 eliminates the vulnerability.
Apply vendor patch (Apache IoTDB 2.0.10). While patching is in progress: restrict database network access to authorized hosts only, disable the pipe processor component if not required, and increase monitoring for unusual database activity.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
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 DataNode (versions 1.3.3 up to but not including 2.0.8) allows attackers who can re
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-42836
GHSA-v4p4-86j5-2f8q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB