---
id: CVE-2026-24014
aliases:
  - PYSEC-2026-2081
title: >-
  Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances
  uses the uploaded Trigger JAR name to build a file path wit…
summary: >-
  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 port is exposed to an untrusted
  network, an…
severity: critical
cvss: 9.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: apache-iotdb
product: apache-iotdb
ecosystem: pip
affected:
  - 'apache-iotdb >= 1.3.3, < 2.0.8'
patched:
  - apache-iotdb 2.0.8
published: '2026-07-06'
updated: '2026-07-08'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/PYSEC-2026-2081'
references:
  - url: 'http://www.openwall.com/lists/oss-security/2026/07/06/12'
  - url: 'https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m'
tags:
  - osv
  - pip
epss: 0.0069
epssPercentile: 0.51397
ingestedAt: '2026-07-09T18:56:35.387Z'
---

## Overview

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 port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process.

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.

## Affected packages

- `apache-iotdb >= 1.3.3, < 2.0.8`

## Remediation

Upgrade to a patched release:

- `apache-iotdb 2.0.8`