dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-64152

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 1.0.0 before 1.3.6, from 2.0.0 before 2.0.7. Users are recommended to upgrade to version 1.3.6 and 2.0.7, 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 restricted directories through manipulation of file paths using '..' sequences in user-supplied input. This enables unauthorized file system access with high severity given the critical CVSS score of 9.1.

MitigationUpgrade Apache IoTDB to version 1.3.6 or 2.0.7 as recommended by the vendor to resolve the path traversal vulnerability.

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 version
    Locate the installed IoTDB version by checking the startup logs, version file, or running 'grep -r version' in the installation directory. Common paths include the conf/iotdb-common.properties or version.txt in the root directory.
    Affected if The installed version is 1.x before 1.3.6 or 2.x before 2.0.7
  2. Verify IoTDB service is active
    Confirm the IoTDB service is running by checking for java processes related to IoTDB (ps aux | grep iotdb) or checking if ports 6667, 6668, or 7777 are in LISTEN state.
    Affected if The IoTDB service is running and accepting connections, exposing the vulnerable file handling code
  3. Check for exposed file operation interfaces
    Identify if REST API, JDBC, or session interfaces that accept file path parameters are enabled. Review conf/iotdb-config.properties for endpoints like 'enable_rest_service' or 'enable_jdbc' set to true.
    Affected if File operation endpoints or APIs are accessible without additional authentication or input validation controls
  4. Review network exposure
    Determine if IoTDB ports (6667, 6668, 7777, 22260) are bound to non-localhost interfaces. Check the 'bind_address' setting in iotdb-config.properties.
    Affected if The service is bound to a public or untrusted network interface rather than localhost only

A user is affected if their Apache IoTDB version is 1.x before 1.3.6 or 2.x before 2.0.7, and the service is running with accessible file operation interfaces exposed to network attackers who can supply path traversal sequences.

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 Apache IoTDB to version 1.3.6 or 2.0.7 as recommended by the vendor to resolve the path traversal vulnerability.

Recommended fix High confidence

1.3.6 for 1.x branch users, or 2.0.7 for 2.x branch users

  1. Identify the currently installed Apache IoTDB version by checking the system configuration or release notes
  2. If running a 1.x version (from 1.0.0 to 1.3.5), plan upgrade to version 1.3.6
  3. If running a 2.x version (from 2.0.0 to 2.0.6), plan upgrade to version 2.0.7
  4. Download the appropriate Apache IoTDB release binary from the official Apache repository (https://iotdb.apache.org/)
  5. Stop the running IoTDB service before performing the upgrade
  6. Backup existing data directories and configuration files
  7. Install the new version following the upgrade documentation
  8. Restart the IoTDB service
Caveat Review Apache IoTDB release notes for any breaking changes or migration requirements between your current version and the target upgrade version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64152 — 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-64152 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