cve.bz

CVE-2026-24014 apache iotdb: Improper Access Control

9.8 criticalEPSS 0.7%Fix available

Critical (9.8) in apache iotdb. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in apache-iotdb 2.0.8.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-284 Improper Access Control
CWE-434 Unrestricted Upload of File with Dangerous Type
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-24014 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-24014?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-24014?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-24014 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-24014

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-24014](https://cve.bz/cve/badge/CVE-2026-24014.svg)](https://cve.bz/cve/CVE-2026-24014)

HTML:

<a href="https://cve.bz/cve/CVE-2026-24014"><img src="https://cve.bz/cve/badge/CVE-2026-24014.svg" alt="CVE-2026-24014"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache IoTDBfrom 1.3.3 before 2.0.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
PYSEC-2026-2081PyPIapache-iotdb>=1.3.3 <2.0.82.0.8

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON