dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-55017

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability in Apache IoTDB allows attackers to access files outside the restricted directory through specially crafted pathname inputs. This improper limitation of pathname to a restricted directory (CWE-22) affects versions 1.0.0-1.3.5 and 2.0.0-2.0.5, enabling unauthorized file system access with potentially severe consequences given the database's role in storing sensitive data.

MitigationUpgrade to Apache IoTDB version 1.3.6 or 2.0.6 which contains the fix for this path traversal vulnerability. Alternatively, implement strict input validation on file path parameters to restrict access to allowed directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache IoTDB installation directory
    Locate the IoTDB installation by checking common paths such as /opt/iotdb, /usr/local/iotdb, or the directory where the startup scripts (start-iotdb.sh, start-server.bat) reside. Use 'find / -name "iotdb" -type d 2>/dev/null' if installation path is unknown.
    Affected if The installation directory cannot be determined or IoTDB is not installed.
  2. Determine installed IoTDB version
    Check the version file typically located at {iotdb_install_dir}/conf/iotdb-version.properties, or run 'ls -la' on the lib directory to find iotdb-core-{version}.jar, or execute './start-iotdb.sh -v' if available.
    Affected if The version falls within 1.0.0-1.3.5 or 2.0.0-2.0.5.
  3. Verify if file import or export functionality is configured
    Inspect the iotdb-config.properties or iotdb-common.properties file in the conf directory for settings related to file operations such as 'sql_tool', 'backup', 'restore', 'import', 'export', or custom storage paths.
    Affected if File import, export, or backup modules are enabled and accessible without additional authentication layers.
  4. Check for exposed file operation endpoints
    Review the iotdb-engine.properties or any REST service configuration for endpoints that accept file path parameters. Look for 'enable_rest_service', 'rest_port', or similar settings, and examine SQL tools or JDBC configurations that may accept file paths.
    Affected if REST service or SQL tools that accept path parameters are exposed and accessible to untrusted users.

You are affected if your installed Apache IoTDB version is 1.0.0 through 1.3.5 or 2.0.0 through 2.0.5 AND you have file import/export, backup, or REST endpoints that accept file path inputs accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apache IoTDB version 1.3.6 or 2.0.6 which contains the fix for this path traversal vulnerability. Alternatively, implement strict input validation on file path parameters to restrict access to allowed directories.

Recommended fix High confidence

Apache IoTDB 1.3.6 or 2.0.6 (depending on your major version branch)

  1. Identify the currently running Apache IoTDB version using the version command or service status
  2. Stop the Apache IoTDB service to prevent data corruption during upgrade
  3. Create a complete backup of the IoTDB installation directory and all data files
  4. Download the appropriate fixed version: version 1.3.6 for 1.x installations, or version 2.0.6 for 2.x installations from the official Apache IoTDB release repository
  5. Extract the new version to the target installation directory, preserving configuration files from the backup
  6. Verify the integrity of the new installation by checking the version number matches the fixed release
  7. Start the upgraded Apache IoTDB service
  8. Verify the service is running correctly and accepting connections
Caveat Review release notes for any configuration or feature changes between your current version and the target fixed version; test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55017 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data