# Authentication Bypass by Spoofing vulnerability in Apache IoTDB.

Advisory record · `PYSEC-2026-2080`

- **Identifiers:** `PYSEC-2026-2080` · `CVE-2026-24013`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-290](https://cwe.mitre.org/data/definitions/290.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 6 Jul 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by OSV at 6 Jul 2026, 09:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `apache-iotdb` (PyPI): affected `>=1.3.3, <2.0.8`; fixed in `2.0.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache IoTDB versions 1.3.3 up to but not including 2.0.8 are affected through the apache-iotdb package. Certain Thrift RPC query handlers do not strictly validate the sessionId parameter, so an attacker who can reach the service over the network can send requests with a forged sessionId and read time-series data without authenticating. Upgrade to apache-iotdb 2.0.8, which fixes the issue.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** 0.0063, the 51st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-2080)

## Sources

- [OSV: PYSEC-2026-2080](https://osv.dev/vulnerability/PYSEC-2026-2080)
- <http://www.openwall.com/lists/oss-security/2026/07/06/11>
- <https://lists.apache.org/thread/6pwkgnqhbm56mvn309f87snm84s0b75y>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2026-2080>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-2080/>. Everything for agents: <https://agentprime.io/llms.txt>.
