Advisory record · PYSEC-2026-2080

Authentication Bypass by Spoofing vulnerability in Apache IoTDB.

CVSS 9.1 CriticalCriticalEPSS 0.0063 · 51st percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

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.

PackageEcosystemAffectedFixed in
apache-iotdbPyPI>=1.3.3, <2.0.82.0.8
Identifiers
PYSEC-2026-2080 · CVE-2026-24013
Weakness (CWE)
CWE-290
Published
6 Jul 2026
Updated
8 Jul 2026

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

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N 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

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

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.