Answer in brief
CVE-2026-24014 records a Critical severity (CVSS 9.8) vulnerability in Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/Apache IoTDB (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/Apache IoTDB (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/Apache IoTDBgeneric | >=1.3.3 <2.0.8 | 2.0.8 |
Published upstream
Jul 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-24014 records a Critical severity (CVSS 9.8) vulnerability in Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/Apache IoTDB (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/Apache IoTDB (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/Apache IoTDBgeneric | >=1.3.3 <2.0.8 | 2.0.8 |
Published upstream
Jul 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.