dbcve.org
IotdbApplication · Apache

CVE-2025-48392

HIGH · 7.5 CVSS v3.1 Published 2025-09-24
Fix available
A fix is available. Upgrade to 2.0.5 or later.
See remediation →
84/100
Remediation priority · High
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
A vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.3.3 through 1.3.4, from 2.0.1-beta through 2.0.4. Users are recommended to upgrade to version 2.0.5, 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 · low confidence

This is a vulnerability in Apache IoTDB, a time-series database. The specific vulnerability type and technical details are not disclosed in the available advisory, but it affects versions 1.3.3 through 1.3.4 and 2.0.1-beta through 2.0.4, with a CVSS score of 7.5 indicating high severity.

MitigationUpgrade Apache IoTDB to version 2.0.5 or later to remediate this vulnerability.

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.3.3, <= 1.3.4>= 2.0.1, < 2.0.5

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 - common paths include /opt/iotdb, /usr/local/iotdb, or a custom installation path. Check for the 'iotdb' or 'apache-iotdb' directory.
    Affected if Unable to locate installation directory - cannot verify version
  2. Check IoTDB version via command line
    In the IoTDB installation bin directory, run: ./start-iotdb.sh -version or ./sbin/cli.sh -version. Alternatively, check the 'VERSION' file in the iotdb directory if it exists.
    Affected if Running version falls within 1.3.3 to 1.3.4 or 2.0.1-beta to 2.0.4
  3. Query version via IoTDB CLI
    Connect to the IoTDB CLI (sbin/start-cli.sh) and execute: 'show version' or query the system metrics endpoint if JMX/metrics are enabled.
    Affected if Returned version matches affected ranges above
  4. Check version in release artifacts or build metadata
    If IoTDB was installed from a package, check the package version using your system package manager: dpkg -l | grep iotdb or rpm -qa | grep iotdb, or check build/deployment manifests.
    Affected if Package version is within the affected ranges

A system is affected if the installed Apache IoTDB version is 1.3.3, 1.3.4, or any version from 2.0.1-beta through 2.0.4. Versions before 1.3.3 or 2.0.5 and later are not affected.

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 2.0.5 or later
Fixed in 2.0.5
Interim mitigation

Upgrade Apache IoTDB to version 2.0.5 or later to remediate this vulnerability.

Recommended fix High confidence

2.0.5

  1. 1. Identify the current Apache IoTDB version in use by checking the installation or configuration.
  2. 2. If running version 1.3.3 or 1.3.4: plan migration to version 2.0.5 or later (note: major version upgrade may require schema/migration review).
  3. 3. If running version 2.0.1 through 2.0.4: upgrade directly to version 2.0.5.
  4. 4. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with existing data and configurations.
  5. 5. Perform a full backup of the existing data and configuration files before initiating the upgrade.
  6. 6. Follow the official Apache IoTDB upgrade documentation for the version transition.
  7. 7. After upgrade, verify that the IoTDB service starts successfully and all expected functionalities work correctly.
Caveat Upgrading from 1.3.x to 2.0.x is a major version change; review migration guides for potential breaking changes in schema, APIs, or configuration formats

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-2025-48392 — 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-48392 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