CVE-2026-24013 json
Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC
published 2026-07-06 4 mo ago modified 2026-10-25 14 d ago also PYSEC-2026-2080 , EUVD-2026-41857
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi apache-iotdb 2.0.8
- Apache Software Foundation Apache IoTDB 2.0.8
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | apache-iotdb | >=1.3.3, <2.0.8 |
2.0.8 |
Affected products
- Apache Software Foundation Apache IoTDB
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
lists.apache.org
/thread/6pwkgnqhbm56mvn309f87snm84s0b75y
vendor-advisory, mailing-list, advisory
-
openwall.com
/lists/oss-security/2026/07/06/11
mailing-list, third-party-advisory, advisory
Sources
- CVE List CVE-2026-24013
- NVD CVE-2026-24013
- OSV PYSEC-2026-2080
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.