# 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...

Advisory record · `PYSEC-2026-2081`

- **Identifiers:** `PYSEC-2026-2081` · `CVE-2026-24014`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-434](https://cwe.mitre.org/data/definitions/434.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Unrestricted file upload](https://agentprime.io/advisories/tag/file-upload.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.8: 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 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

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

- 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-2081)

## Sources

- [OSV: PYSEC-2026-2081](https://osv.dev/vulnerability/PYSEC-2026-2081)
- <http://www.openwall.com/lists/oss-security/2026/07/06/12>
- <https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m>

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-2081>, 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-2081/>. Everything for agents: <https://agentprime.io/llms.txt>.
