CVE-2025-55017: Apache IoTDB · Path Traversal
Affects Apache IoTDBSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.0.6 or 1.3.6 as a priority.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.6, 1.3.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade Apache IoTDB to 2.0.6 or 1.3.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache IoTDB | Affected
| Fixed in
|
| Apache Software FoundationApache IoTDB | Affected
| Fixed in
|
Mavenorg.apache.iotdb/iotdbpkg:maven/org.apache.iotdb/iotdbOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache IoTDB to version 1.3.6 or 2.0.6 or later, which contain fixes for this path traversal vulnerability. No other mitigation details or temporary fixes are provided. Patch status is confirmed by the vendor's recommended upgrade versions.
Description
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 2.0.0 before 2.0.6, from 1.0.0 before 1.3.6. Users are recommended to upgrade to version 1.3.6 and 2.0.6, which fixes the issue.