dbcve.org
CWE-294Weakness · CWE-294

CVE-2026-28564

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
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 6 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
Insufficient Session Expiration, Authentication Bypass by Capture-replay vulnerability in Apache IoTDB. REST Basic Authentication Accepts Stale Cached Credentials 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 confidence

Apache IoTDB versions 1.0.0 through 2.0.9 contain an authentication bypass vulnerability in the REST Basic Authentication mechanism. The system accepts stale cached credentials due to insufficient session expiration, allowing capture-replay attacks where attackers can reuse old authentication tokens or credentials to gain unauthorized access.

MitigationUpgrade Apache IoTDB to version 2.0.10 or later, which contains the fix for this authentication bypass and session expiration issue.

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
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 version
    Locate the IoTDB installation and check the version file (typically VERSION in the root directory or run the CLI and check the startup banner). Compare against the affected range.
    Affected if version is 1.0.0 through 2.0.9 (before 2.0.10)
  2. Confirm REST service is enabled
    Check the IoTDB configuration file (iotdb-common.properties or iotdb-config.properties in the conf directory) for the enableRestService setting.
    Affected if REST service is enabled (enableRestService=true or not explicitly set to false)
  3. Review session expiration configuration
    Examine the same configuration file for session or token timeout settings (look for parameters like sessionTimeout, tokenExpiration, or authTimeout).
    Affected if session expiration is set to a very long duration, zero, or is not explicitly configured (allowing stale credentials to persist)
  4. Check Basic Authentication cache behavior
    Inspect if the REST Basic Authentication mechanism is using cached credentials by reviewing the authentication handler configuration or testing with a known-expired credential if session state is observable.
    Affected if system accepts credentials beyond their valid lifetime or caches authentication state without expiration enforcement

You are affected if Apache IoTDB version is between 1.0.0 and 2.0.9, the REST service is enabled, and session/token expiration is not properly enforced.

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 2.0.10 or later, which contains the fix for this authentication bypass and session expiration issue.

Recommended fix High confidence

2.0.10

  1. 1. Backup all IoTDB data and configuration files before upgrading
  2. 2. Download Apache IoTDB version 2.0.10 from the official Apache IoTDB downloads page (https://iotdb.apache.org/download/)
  3. 3. Stop the running IoTDB service gracefully
  4. 4. Replace the existing IoTDB installation directory with the new 2.0.10 installation
  5. 5. Restore your backed-up configuration files (such as iotdb.conf and log4j.properties) to the new installation
  6. 6. Verify the upgrade was successful by checking the IoTDB version at startup
  7. 7. Start the IoTDB service and confirm REST API authentication now properly expires stale credentials
  8. 8. Test REST Basic Authentication to ensure it no longer accepts stale cached credentials
Caveat Review Apache IoTDB 2.0.10 release notes for any breaking changes or migration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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