# CVE-2026-24013: Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC

> Attackers can bypass authentication in Apache IoTDB by forging session IDs in Thrift RPC requests, allowing unauthorized access to time-series data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-qx5v-jm63-wqfj, PYSEC-2026-2080

## What is CVE-2026-24013?

CVE-2026-24013 is a critical authentication bypass vulnerability in Apache IoTDB, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-24013?

1 open source package ship an affected version, including apache-iotdb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-iotdb` | PyPI | From 1.3.3 | 2.0.8 |

Products: Apache Iotdb.

## How do I fix CVE-2026-24013?

Upgrade apache-iotdb to 2.0.8 or later.

## Is CVE-2026-24013 being exploited?

There is no known exploitation of CVE-2026-24013 in the wild and no public exploit code.

## Other vulnerabilities in Apache IoTDB

- [CVE-2026-24014](https://insights.sbomify.com/CVE-2026-24014/): Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write (critical 9.8)
- [CVE-2026-24015](https://insights.sbomify.com/CVE-2026-24015/): Apache IoTDB: Insecure Default Configuration Vulnerability (critical 9.8)
- [CVE-2026-24713](https://insights.sbomify.com/CVE-2026-24713/): Apache IoTDB: JEXL Expression Injection Vulnerability (critical 9.8)
- [CVE-2024-24780](https://insights.sbomify.com/CVE-2024-24780/): Apache IoTDB: Remote Code Execution with untrusted URI of User-defined function (critical 9.8)
- [CVE-2023-46226](https://insights.sbomify.com/CVE-2023-46226/): Apache IoTDB: Remote Code Execution (RCE) risk via the UDF (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24013 and fix it if it is affected.

What it is: CVE-2026-24013 is a critical authentication bypass vulnerability in Apache IoTDB, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24013 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-iotdb (PyPI): affected from 1.3.3; fixed in 2.0.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24013/ (Markdown: https://insights.sbomify.com/CVE-2026-24013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24013
- OSV: https://osv.dev/vulnerability/CVE-2026-24013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24013/
Summaries are generated and may contain mistakes; the official description above is the record.