dbcve.org
IotdbApplication · Apache

CVE-2026-24713

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-09
Fix available
A fix is available. Upgrade to 1.3.7 / 2.0.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Input Validation vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 1.3.7, from 2.0.0 before 2.0.7. Users are recommended to upgrade to version 1.3.7 or 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 · moderate confidence

Improper Input Validation vulnerability in Apache IoTDB allows attackers to potentially exploit insufficient validation of input data, which could lead to remote code execution or data corruption given the critical 9.8 CVSS score.

MitigationUpgrade Apache IoTDB to version 1.3.7 or 2.0.7 to remediate this vulnerability, as these versions contain the fix for the improper input validation flaw.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IotdbApplication
Affected:>= 1.0.0, < 1.3.7>= 2.0.0, < 2.0.7

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
High

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

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 location
    Locate the IoTDB installation directory, typically found in /opt/iotdb, /usr/local/iotdb, or a user-defined installation path. Check for the presence of the iotdb binaries or the conf folder.
    Affected if Cannot locate IoTDB installation or the directory does not exist.
  2. Determine installed IoTDB version
    Check the version file or use the version command. Common methods include: (1) Check VERSION file in the installation root if it exists, (2) Run 'start-cli.sh -v' or 'iotdb-cli.sh -v' if available, (3) Check the conf/iotdb-config.properties or iotdb-engine.properties for version properties.
    Affected if Unable to retrieve version information.
  3. Compare version against affected ranges
    If version is obtained, parse it and compare: the version is affected if it is (>= 1.0.0 AND < 1.3.7) OR (>= 2.0.0 AND < 2.0.7). For example, versions 1.2.0, 1.3.0, 1.3.6, 2.0.0, 2.0.5 are affected. Versions 1.3.7 and above, or 2.0.7 and above, are NOT affected.
    Affected if The installed version falls within >= 1.0.0 and < 1.3.7, or within >= 2.0.0 and < 2.0.7.
  4. Verify the vulnerability trigger condition (optional)
    This vulnerability requires the IoTDB server to be running and accepting input data. If IoTDB is only installed but not actively running as a service, the attack surface is reduced. Check if the server process (iotdb or tsfile) is running.
    Affected if The server is actively running and the version is within the affected ranges.

A user is affected if Apache IoTDB is installed with a version that is 1.0.0 or higher but below 1.3.7, or 2.0.0 or higher but below 2.0.7, and the service is running.

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
Upgrade available Upgrade to 1.3.7 / 2.0.7 or later
Fixed in 1.3.72.0.7
Interim mitigation

Upgrade Apache IoTDB to version 1.3.7 or 2.0.7 to remediate this vulnerability, as these versions contain the fix for the improper input validation flaw.

Recommended fix High confidence

1.3.7 or 2.0.7 (depending on major version branch)

  1. Identify the current version of Apache IoTDB in use by checking the installation directory or configuration files
  2. Determine which major version branch is in use (1.x or 2.x) to select the appropriate upgrade target
  3. Back up all existing data, configuration files, and the database storage directory before proceeding
  4. Stop all IoTDB services to prevent data corruption during upgrade
  5. Download the corresponding fixed version: 1.3.7 for 1.x installations or 2.0.7 for 2.x installations from the official Apache IoTDB distribution
  6. Replace the existing IoTDB installation with the new version, preserving the configuration files from the backup
  7. Review and update any configuration parameters if needed for compatibility with the new version
  8. Start the IoTDB service and verify successful startup
Caveat Standard minor version upgrades typically maintain backward compatibility with data and most configs; review release notes for any specific migration notes

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

Fix this in Iotdb 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 the upgrade done

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-2026-24713 — 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-2026-24713 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