EUVD-2026-41857
GHSA-qx5v-jm63-wqfj
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Unauthenticated network RPC with no interaction gives AV:N/AC:L/PR:N/UI:N; description substantiates only data reading, so C:H but I:N/A:N.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
6DescriptionCVE.org
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This allows authentication bypass and unauthorized reading of time-series data.
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
AnalysisAI
Authentication bypass via sessionId spoofing in Apache IoTDB (1.3.3 through versions before 2.0.8) lets a remote, unauthenticated attacker forge the sessionId parameter on certain Thrift RPC query handlers and retrieve valid query results without ever calling openSession. This exposes stored time-series data to arbitrary readers. No public exploit identified at time of analysis, and EPSS is low (0.20%, 10th percentile) despite the 9.1 CVSS, so exploitation is not confirmed in the wild.
Technical ContextAI
Apache IoTDB is an open-source time-series database purpose-built for IoT and industrial sensor telemetry, exposing its client API over an Apache Thrift RPC service. Sessions are normally established through an openSession call that authenticates the client and issues a sessionId used on all subsequent RPC calls. This flaw is a CWE-290 (Authentication Bypass by Spoofing): specific Thrift query handlers trust the caller-supplied sessionId without verifying it corresponds to an authenticated, server-issued session, so a client can present a fabricated identifier and be treated as a valid session. The root cause is missing server-side session-state validation on those RPC entry points rather than a cryptographic or transport weakness.
RemediationAI
Vendor-released patch: upgrade Apache IoTDB to version 2.0.8, which the Apache project states fixes the issue - this is the primary and recommended remediation. Where an immediate upgrade is not feasible, reduce exposure by restricting network access to the IoTDB Thrift RPC service port (default 6667) to trusted client hosts only via firewall or security-group rules, and place the database behind a VPN or bastion rather than on any untrusted or internet-facing segment; note this does not fix the underlying bypass and offers no protection against an attacker already inside the trusted network. Consult the Apache advisory (https://lists.apache.org/thread/6pwkgnqhbm56mvn309f87snm84s0b75y) and the oss-security disclosure (https://seclists.org/oss-sec/2026/q3/68) before deploying.
More in Apache Iotdb
View allUnsafe 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 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
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
Privilege escalation in Apache IoTDB 2.0.8 through 2.0.9 allows any authenticated low-privilege user to rename their own
Path traversal in Apache IoTDB (1.0.0 before 1.3.6 and 2.0.0 before 2.0.7) allows remote attackers to read and write fil
Path traversal in Apache IoTDB (versions 1.0.0–1.3.5 and 2.0.0–2.0.5) lets remote unauthenticated attackers reference fi
Same weakness CWE-290 – Authentication Bypass by Spoofing
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today