CVE-2026-40005
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 · uneditedImproper 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.
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 confidenceApache IoTDB versions 1.0.0 through 2.0.9 contain a path traversal vulnerability allowing authenticated or unauthenticated attackers to write arbitrary files to any directory where the IoTDB process has write permissions by manipulating file paths in unsafe API calls.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IoTDB versionRun the IoTDB CLI and execute 'SHOW VERSION' or check the version displayed on startup. Alternatively, inspect the iotdb-version.properties file in the installation directory.Affected if The installed version is 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, or any version from 1.4.0 through 2.0.9 inclusive.
-
Verify API service exposureCheck if the IoTDB REST API or RPC service ports (default 6667, 10100, 8181 commonly used) are listening on network interfaces accessible to untrusted users. Use 'netstat -tlnp' or 'ss -tlnp' to list listening ports.Affected if The IoTDB API service is bound to a publicly accessible IP address or an untrusted network segment.
-
Assess write permissions on IoTDB data directoriesIdentify directories where IoTDB writes data (commonly under 'data' folder in installation directory). Check filesystem permissions with 'ls -la' and verify which system user owns the IoTDB process.Affected if The IoTDB process runs with elevated privileges or has write access to system directories outside its designated data folder.
-
Review API request logging for suspicious path parametersExamine IoTDB logs (in 'logs' directory) for API requests containing '../' sequences or absolute file paths in parameters. Look for patterns indicating path traversal attempts.Affected if Log entries show requests with manipulated file path parameters that bypass expected directory constraints.
The environment is affected if the installed Apache IoTDB version is 1.0.0 through 2.0.9 and the API service is network-accessible with permissions that allow writing to unintended directories.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Apache IoTDB version 2.0.10 or later to obtain the patched version with proper path validation.
2.0.10
- Stop the Apache IoTDB service
- Backup the current IoTDB installation and all data
- Download Apache IoTDB version 2.0.10 from the official Apache IoTDB downloads page (https://iotdb.apache.org/Download/)
- Install version 2.0.10 following the upgrade instructions in the Apache IoTDB documentation
- Review release notes for any required configuration changes
- Start the IoTDB service and verify it operates correctly
- Test that the path traversal vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40005 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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