Skip to main content

Apache IoTDB EUVDEUVD-2026-42833

| CVE-2026-40005 CRITICAL
Path Traversal (CWE-22)
2026-07-10 apache GHSA-h3q7-wmrf-p69f
9.1
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed IoTDB API over network
  2. Delivery
    Craft request with traversing pathname
  3. Exploit
    Trigger unsafe file-write API
  4. Execution
    Write payload to executable/config path
  5. Impact
    Achieve code execution or data tampering

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network access to the Apache IoTDB service and the ability to invoke the specific unsafe file-writing API that accepts an unsanitized pathname; per CVSS PR:N/UI:N/AC:L this needs no authentication, no user interaction, and no special deployment mode against affected 1.0.0-2.0.9 servers. What limits real-world impact: the write is constrained to locations where the IoTDB process account has write permission, so a least-privileged deployment narrows the reachable targets; the API endpoint must be network-reachable (an instance bound to localhost or behind a firewall/authentication proxy is not exposed); and converting the write into code execution requires a writable path that is subsequently executed or loaded. Note that CVSS PR:N assumes the API is reachable without auth - if your deployment gates the IoTDB endpoint behind authentication, that assumption should be re-validated.

Impact

Signals are mixed and warrant scrutiny. The CVSS vector rates this network-reachable, low-complexity, and unauthenticated (PR:N) with total technical impact - corroborated by CISA SSVC scoring Technical Impact 'total' and Automatable 'yes'. However, the exploitation-side signals are cool: SSVC Exploitation is 'none', the issue is absent from CISA KEV, EPSS is only 0.16% (5th percentile), and no POC has surfaced. This points to a genuinely high-capability primitive (arbitrary file write, automatable) that is not yet being exploited in the wild - a patch-soon rather than patch-tonight posture in general, but higher urgency where IoTDB is exposed to untrusted networks. One caveat: the vendor CVSS marks A:N (no availability impact), yet an arbitrary file write that can overwrite configuration or data files could plausibly affect availability or integrity of the database itself, so A:N should be validated against your deployment. PR:N assumes the vulnerable API is reachable without authentication, which depends on whether the IoTDB endpoint is access-controlled in your environment.

Exploit ScenarioDerived

An attacker with network reach to an exposed Apache IoTDB instance sends a crafted request to the unsafe API with a path parameter containing traversal sequences (e.g. '../../') or an absolute path, causing the server to write attacker-controlled content outside the intended directory. By dropping a file into a location that is later executed or loaded - a startup script, a configuration file, or a web-served path - the attacker can pivot from arbitrary write to code execution or data tampering. No public POC has been identified, but the low attack complexity and automatable nature would make weaponization straightforward once details circulate.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv3 – Jul 10, 2026

Arbitrary file write in Apache IoTDB (versions 1.0.0 through 2.0.9) lets remote attackers plant files anywhere the IoTDB process can write by abusing an unsafe API that fails to sanitize user-supplied pathnames. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates unauthenticated network exploitation with high confidentiality and integrity impact, and controlled file placement can escalate to code execution or overwrite of critical files. No public exploit has been identified at time of analysis, and EPSS is low (0.16%, 5th percentile) despite the 9.1 severity.

Earlier versions of this analysis (2)
v2 Jul 10, 2026 - 16:28 cvss changed CVSS 9.1

Arbitrary file write in Apache IoTDB (versions 1.0.0 through 2.0.9) allows a remote, unauthenticated attacker to write files to any location the IoTDB process can access via an unsafe API that fails to sanitize pathnames. Rated CVSS 9.1 with high confidentiality and integrity impact, this path traversal flaw is fixed in 2.0.10; there is no public exploit identified at time of analysis, and the EPSS probability is low (0.16%, 5th percentile).

v1 Jul 10, 2026 - 08:26

Arbitrary file write in Apache IoTDB (versions 1.0.0 through 2.0.9) allows an attacker abusing an unsafe API to write files to any location the IoTDB process can access via path traversal, potentially enabling configuration tampering, data corruption, or code execution. The flaw was reported by the Apache project itself and fixed in 2.0.10; no public exploit was identified at time of analysis, and it is not listed in CISA KEV. Because IoTDB is a time-series database commonly deployed in IoT/industrial telemetry pipelines, a successful write primitive against core storage or config files is high-impact.

RemediationAI

Vendor-released patch: upgrade to Apache IoTDB 2.0.10, which fixes the path traversal, per the Apache advisory (https://lists.apache.org/thread/zw2vkbmy5xkf5y8g237v81hrs4c6b5lq). This is the primary and recommended action for all deployments running 1.0.0 through 2.0.9. If immediate upgrade is not possible, reduce exposure by restricting network access to the IoTDB service - bind it to trusted internal interfaces only and block external access to its client/RPC ports at the firewall - and enforce least-privilege on the OS account running the IoTDB process so a successful write cannot reach OS-critical or web-served directories (trade-off: tightening that account's write scope requires re-validating data and WAL directory permissions to avoid disrupting normal operation). These are compensating controls only; they do not remove the vulnerable API, so 2.0.10 should be applied as soon as feasible.

Affected VersionsENISA

Apache IoTDB 1.0.0 <2.0.10

Affected Packages

euvd apache_iotdb fix: 2.0.10

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache IoTDB is an open-source time-series database management system used to store and query telemetry from IoT, industrial (IIoT), and sensor deployments. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, 'Path Traversal'): an exposed API accepts a filename/path parameter and builds a filesystem path without normalizing or constraining it to an intended directory, so traversal sequences (e.g. '../') or absolute paths let an attacker escape the intended write location. The affected CPE is cpe:2.3:a:apache_software_foundation:apache_iotdb, covering all 1.0.0-2.0.9 releases of the server. Because the write executes with the privileges of the IoTDB process, the blast radius is bounded by that process's filesystem permissions.

Know when Apache Iotdb gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 9.1 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 9.1 CRITICAL

Unauthenticated network path-traversal write (AV:N/AC:L/PR:N/UI:N); primary impact is integrity (I:H) with availability risk (A:H) from overwriting data/config, no direct read so C:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

5
Analysis Updated
Jul 10, 2026 - 16:28 vuln.today
v3 - CVSS changed
Analysis Updated
Jul 10, 2026 - 16:28 vuln.today
v2 - CVSS changed
Severity Changed
Jul 10, 2026 - 16:22 NVD
HIGH CRITICAL
CVSS changed
Jul 10, 2026 - 16:22 NVD
9.1 (HIGH) 9.1 (CRITICAL)
Patch available
Jul 10, 2026 - 09:16 EUVD

DescriptionCVE.org

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache IoTDB. An attacker can write arbitrary files anywhere the IoTDB process has write permissions with unsafe API.

This issue affects Apache IoTDB: from 1.0.0 before 2.0.10.

Users are recommended to upgrade to version 2.0.10, which fixes the issue.

Executive ViewAI

Why It Matters

Apache IoTDB versions 1.0.0 through 2.0.9 contain a critical arbitrary file write vulnerability allowing unauthenticated remote attackers to place malicious files on affected systems, with potential escalation to code execution. Organizations running these versions face immediate risk of system compromise and unauthorized data modification. Urgent patching across all affected IoTDB deployments is required.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
popular open-source time-series DB for IoT/industrial, not ubiquitous enterprise-wide
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

CVE-2026-59562 CRITICAL
9.8 Oct 21

Missing authentication for a critical function in Apache IoTDB 2.0.0 through 2.0.10 lets unauthenticated remote attacker

CVE-2026-58663 CRITICAL
9.8 Oct 21

Unauthenticated remote attackers can bypass authentication in Apache IoTDB 2.0.0 through 2.0.10 through the Thrift RPC s

CVE-2026-40008 CRITICAL
9.8 Jul 10

Unsafe reflection in Apache IoTDB's pipe processor lets a user-supplied fully qualified Java class name be loaded and in

CVE-2026-28564 CRITICAL
9.8 Jul 10

Authentication bypass via capture-replay in Apache IoTDB (1.0.0 through 2.0.9) lets attackers reuse stale credentials ag

CVE-2026-24014 CRITICAL
9.8 Jul 06

Arbitrary file write in Apache IoTDB DataNode (versions 1.3.3 up to but not including 2.0.8) allows attackers who can re

CVE-2026-59229 HIGH
8.8 Oct 21

Apache IoTDB 2.0.0 through 2.0.11 mishandles identity in its Legacy Pipe receiver: the handshake and sendPipeData handle

CVE-2026-44630 HIGH
7.5 Aug 10

Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the databa

CVE-2026-40006 HIGH
7.5 Jul 10

Unauthenticated denial of service in Apache IoTDB (1.0.0 through 2.0.9) allows remote attackers to crash or degrade the

CVE-2026-24012 HIGH
7.5 Jul 06

Denial of service in Apache IoTDB versions 1.3.3 through 2.0.7 lets remote attackers crash the DataNode process by submi

CVE-2026-40452 HIGH
7.5 Jul 10

Authorization bypass in Apache IoTDB's REST API endpoint /rest/v2/fastLastQuery allows authenticated users to access las

CVE-2026-40007 HIGH
7.5 Jul 10

Denial of service in Apache IoTDB versions 1.0.0 up to (but not including) 2.0.10 lets an unauthenticated network attack

CVE-2026-24013 CRITICAL
9.1 Jul 06

Authentication bypass via sessionId spoofing in Apache IoTDB (1.3.3 through versions before 2.0.8) lets a remote, unauth

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy