Skip to content
Heist/ feed
Back to feed
Critical

Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-24014
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 16:54 UTC · Revision 1

Source evidence

Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write

core-osv · Original source

Published 6 Jul 2026, 08:34 UTC

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.

osv:CVE-2026-24014
Complete source record
{
  "id": "d02cb956839226f483500f8ee26c673ae71547282d54cdde23624a2473c7ef5c",
  "url": "https://osv.dev/vulnerability/CVE-2026-24014",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write",
    "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 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.",
    "evidence": "osv:CVE-2026-24014",
    "products": [],
    "severity": "critical",
    "structured": {
      "id": "CVE-2026-24014",
      "aliases": [
        "CVE-2026-24014",
        "PYSEC-2026-2081"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/apache/iotdb",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ad95a7ee57990f7ce5d1503643a3b20936da51e7"
                },
                {
                  "fixed": "b88b5dc62ffb0329fdc4dfd479fc46e9cf416a56"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:apache:iotdb:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "1.3.3"
                      },
                      {
                        "fixed": "2.0.8"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-24014.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:37.600687610Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/24xxx/CVE-2026-24014.json",
        "https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-24014"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-284",
          "CWE-434"
        ],
        "cna_assigner": "apache",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "1.3.3"
                  },
                  {
                    "fixed": "2.0.8"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/24xxx/CVE-2026-24014.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-24014",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 504956,
  "published_at": "2026-07-06T08:34:26.447+00:00"
}