dbcve.org
IotdbApplication · Apache

CVE-2026-24013

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 2.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 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
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This allows authentication bypass and unauthorized reading of time-series data. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, 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

Apache IoTDB Thrift RPC query handlers fail to properly validate the sessionId parameter, allowing attackers to forge session IDs and bypass authentication. This enables unauthorized access to time-series data without performing the openSession authentication. The vulnerability stems from insufficient validation logic in the RPC layer.

MitigationUpgrade Apache IoTDB to version 2.0.8 or later to patch the sessionId validation vulnerability. If immediate upgrade is not possible, consider restricting network access to Thrift RPC endpoints.

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, < 2.0.8

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 installed Apache IoTDB version
    Run 'iotdb --version' or check the iotdb classpath jar files, or inspect the 'iotdb-common' jar manifest for the version. Also check the iotdb-config.yaml or iotdb-env.sh files for version references.
    Affected if The installed version is between 1.3.3 and 2.0.7 inclusive (versions < 2.0.8)
  2. Verify Thrift RPC service is enabled
    Check the IoTDB configuration file (iotdb-config.properties or iotdb-config.yaml) for the 'rpc_port' setting (default 6667) and confirm the RPC service is not disabled. Look for 'enable_rpc' or similar configuration flags.
    Affected if The Thrift RPC service is enabled and configured with an accessible port
  3. Confirm RPC endpoint is network accessible
    Check network binding configuration in iotdb-config.properties for 'rpc_address' (default '0.0.0.0' or 'localhost'). Use 'netstat -an | grep 6667' or 'ss -tlnp | grep 6667' to verify the RPC port is listening and exposed.
    Affected if The RPC port binds to 0.0.0.0 or is otherwise reachable from untrusted networks
  4. Check authentication configuration
    Review iotdb-config.properties for 'auth_enabled' setting. By default, IoTDB may have authentication disabled in development modes.
    Affected if Authentication is disabled or set to false

The environment is affected if running IoTDB version 1.3.3 through 2.0.7 with the Thrift RPC service enabled and network-accessible, regardless of authentication settings since the sessionId validation flaw bypasses authentication entirely.

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.8 or later
Fixed in 2.0.8
Interim mitigation

Upgrade Apache IoTDB to version 2.0.8 or later to patch the sessionId validation vulnerability. If immediate upgrade is not possible, consider restricting network access to Thrift RPC endpoints.

Recommended fix High confidence

2.0.8

  1. 1. Back up your existing Apache IoTDB installation, configuration files, and data directory to prevent data loss during upgrade.
  2. 2. Download Apache IoTDB version 2.0.8 from the official Apache IoTDB downloads page (https://iotdb.apache.org/Download/).
  3. 3. Stop the currently running IoTDB service gracefully to avoid data corruption.
  4. 4. Install or replace the IoTDB binaries with version 2.0.8, ensuring the configuration files are compatible or updated as needed for the new version.
  5. 5. Start the upgraded IoTDB service and verify it initializes without errors.
  6. 6. Validate that the authentication bypass vulnerability is resolved by confirming that unauthenticated requests with forged sessionIds are now rejected.

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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