Arbitrary class instantiation via pipe transfer RPC
Published Jul 10, 2026 · Updated Jul 10, 2026
Unsafe reflection in Apache IoTDB 1.0.0 through 2.0.9 allows remote attackers to instantiate arbitrary Java classes via pipe transfer RPC. The pipe processor passes a request-supplied fully qualified class name to Class.forName().newInstance() without validation or an allowlist. The request requires no authentication or user interaction, and successful exploitation instantiates an attacker-selected class in the server process.
Summary
What happened
Unsafe reflection in Apache IoTDB 1.0.0 through 2.0.9 allows remote attackers to instantiate arbitrary Java classes via pipe transfer RPC. The pipe processor passes a request-supplied fully qualified class name to Class.forName().newInstance() without validation or an allowlist. The request requires no authentication or user interaction, and successful exploitation instantiates an attacker-selected class in the server process.
The record
- CVE
- CVE-2026-40008
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache IoTDB
- Classifications
- CWE-470, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <2.0.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo