Advisory record · PYSEC-2026-2081

Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC por...

CVSS 9.8 CriticalCriticalEPSS 0.0069 · 53rd percentile

Critical, because:

  • CVSS score 9.8: 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-2081 · CVE-2026-24014
Weakness (CWE)
CWE-284 · CWE-434
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 from 1.3.3 before 2.0.8 are vulnerable. The DataNode's internal RPC interface for creating Trigger instances does not sufficiently validate the uploaded Trigger JAR name used to build a file path. An attacker with network access to an exposed internal DataNode RPC port could use path traversal in the JAR name to write arbitrary files with the permissions of the IoTDB process. Upgrade to version 2.0.8.

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.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H OSV
  • CISA KEV Not listed.
  • EPSS 0.0069, the 53rd 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.