VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

apache-iotdb: vulnerability history, versions and safety

apache-iotdb is a package in the PyPI ecosystem. Vulert records 14 vulnerabilities for it across 46 releases, from Sep 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded U14
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 06 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all apache-iotdb vulnerabilities

Vulert verdict on apache-iotdb 2.0.11 i

Updated on 23 Oct 2026

Careful: 2.0.11 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.0.11 — affected i
  • Vulnerabilities on record 14 over 3 years · 3 in the last year i
  • Latest disclosure 06 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 10 packages i
  • Stars 6,420 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for apache-iotdb, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.11 14 Sep 2026 U2 Apache-2.0 No Details →
2.0.10 09 Jul 2026 U2 Apache-2.0 No Details →
2.0.8 14 Apr 2026 U2 Apache-2.0 No Details →
2.0.6 20 Jan 2026 U3 Apache-2.0 Yes Details →
2.0.5 22 Aug 2025 U3 Apache-2.0 Yes Details →
2.0.4 09 Jul 2025 U4 Apache-2.0 Yes Details →
2.0.3 30 May 2025 U4 Apache-2.0 Yes Details →
2.0.4.dev0 27 Apr 2025 U4 Apache-2.0 Yes Details →
2.0.2 17 Apr 2025 U4 Apache-2.0 Yes Details →
1.3.4 17 Apr 2025 U4 Apache-2.0 Yes Details →
2.0.1b0 05 Mar 2025 U4 Apache-2.0 Yes Details →
1.3.3 20 Nov 2024 U7 Apache-2.0 No Details →
1.3.2.post0 16 Jul 2024 U4 Apache-2.0 No Details →
1.3.2 01 Jul 2024 U4 Apache-2.0 No Details →
1.3.0 02 Jan 2024 U4 Apache-2.0 No Details →
1.2.1 19 Sep 2023 U5 Apache-2.0 No Details →
1.2.0 08 Sep 2023 U5 Apache-2.0 No Details →
1.1.2 28 Jul 2023 U5 Apache-2.0 No Details →
1.1.0 04 Apr 2023 U6 Apache-2.0 No Details →
0.13.5.1 23 Mar 2023 U3 Apache-2.0 No Details →
0.13.5 23 Mar 2023 U3 Apache-2.0 No Details →
1.0.1 24 Feb 2023 U6 Apache-2.0 No Details →
0.13.3 19 Dec 2022 U4 Apache-2.0 No Details →
1.0.0 06 Dec 2022 U6 Apache-2.0 No Details →
0.13.2 08 Sep 2022 U6 Apache-2.0 No Details →
0.13.1 09 Aug 2022 U6 Apache-2.0 No Details →
0.12.6 13 Jul 2022 U5 Apache-2.0 No Details →
0.14.0rc1 11 Jul 2022 U3 Apache-2.0 No Details →
0.13.0.post1 21 Mar 2022 U7 Apache-2.0 No Details →
0.13.0 20 Mar 2022 U7 Apache-2.0 No Details →
0.12.5 08 Mar 2022 U5 Apache-2.0 No Details →
0.12.4 25 Dec 2021 U5 Apache-2.0 No Details →
0.12.3 18 Nov 2021 U5 Apache-2.0 No Details →
0.12.2 13 Sep 2021 U5 Apache-2.0 No Details →
0.12.1 22 Jun 2021 U4 Apache-2.0 No Details →
0.11.4 22 Jun 2021 U4 Apache-2.0 No Details →
0.12.0 16 Apr 2021 U4 Apache-2.0 No Details →
0.11.3 16 Apr 2021 U4 Apache-2.0 No Details →
0.11.2 22 Jan 2021 U4 Apache-2.0 No Details →
0.11.1 14 Dec 2020 U4 Apache-2.0 No Details →
0.11.0 26 Nov 2020 U4 Apache-2.0 No Details →
0.10.1 23 Aug 2020 U4 Apache-2.0 No Details →
0.10.0 28 Jun 2020 U4 Apache-2.0 No Details →
0.9.3 15 May 2020 U3 Apache-2.0 No Details →
0.9.2 26 Apr 2020 U3 Apache-2.0 No Details →
0.9.0 08 Dec 2019 U3 Apache-2.0 No Details →

All 46 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2023 4
  • 2024 1
  • 2025 3
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for apache-iotdb

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-24014: Apache IoTDB Arbitrary File Write Vulnerability 9.8 critical 2.0.8 06 Jul 2026
CVE-2023-46226: Remote Code Execution vulnerability in Apache IoTDB 9.8 critical 1.3.0 15 Jan 2024
CVE-2026-24013: Apache IoTDB Authentication Bypass Vulnerability 9.1 critical 2.0.8 06 Jul 2026
CVE-2022-38369: Apache IoTDB Session ID Attack Vulnerability 8.8 high 0.13.1 05 Sep 2022
CVE-2022-38370: Apache IoTDB grafana-connector 0.13.0 Authorization Bypass Vulnerability 7.5 high No fix published 05 Sep 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About apache-iotdb

Is apache-iotdb safe to use?

Vulert records 14 vulnerabilities for apache-iotdb in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 14 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is apache-iotdb's Vulert package health score?

Vulert scores apache-iotdb 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of apache-iotdb affected?

Yes. 2.0.11, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of apache-iotdb should I use?

2.0.11 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does apache-iotdb have?

14 vulnerabilities are recorded for apache-iotdb in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 14 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new apache-iotdb vulnerabilities disclosed?

3 vulnerabilities were recorded for apache-iotdb in the last 12 months, and the oldest entry in this database dates to 05 Sep 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of apache-iotdb are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor apache-iotdb for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the apache-iotdb version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.