dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-40006

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
Memory Allocation with Excessive Size Value, Allocation of Resources Without Limits or Throttling, Missing Authentication for Critical Function vulnerability in Apache IoTDB. When pipe_air_gap_receiver_enabled=true, the IoTDB AirGap pipe receiver accepts raw TCP connections on port 9780 with no authentication. The readLength method reads an attacker-controlled 32-bit integer from the socket and readData passes it directly to new byte[length] with no upper-bound check. An unauthenticated attacker can cause the JVM to attempt an allocation of up to 2,147,483,647 bytes per connection, exhausting heap memory and crashing or severely degrading the DataNode process. 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 AirGap pipe receiver (port 9780) lacks authentication and performs no bounds validation on attacker-controlled length values in readLength/readData methods, allowing unauthenticated heap exhaustion via new byte[length] where length can be up to 2,147,483,647.

MitigationUpgrade IoTDB to version 2.0.10 or disable the AirGap pipe receiver (pipe_air_gap_receiver_enabled=false) if not required.

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
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 IoTDB version
    Run 'iotdb --version' or check the version file in the IoTDB installation directory (e.g., libs/iotdb-version.txt) or query the running instance via its CLI with 'SHOW VERSION'
    Affected if Version is earlier than 2.0.10 (e.g., 2.0.0 through 2.0.9) or any 1.x release
  2. Verify AirGap pipe receiver configuration
    Check the iotdb-config.properties file (commonly in conf/ directory) for the setting 'pipe_air_gap_receiver_enabled' or query it at runtime using the SQL command 'SHOW CONFIGURATION pipe_air_gap_receiver_enabled'
    Affected if The value is set to 'true' or the config is missing (defaults to true in vulnerable versions)
  3. Confirm port 9780 is listening
    Run 'netstat -tlnp | grep 9780' or 'ss -tlnp | grep 9780' on the IoTDB host to check if the AirGap pipe receiver port is open and accepting connections
    Affected if Port 9780 is LISTEN or in use by the IoTDB process
  4. Check for exposed network access
    Verify that port 9780 is accessible from untrusted networks by reviewing firewall rules (iptables, security groups, or network ACLs) or running a port scan from an external host
    Affected if Port 9780 is accessible from networks outside the trusted administrative zone

You are affected if running any IoTDB version below 2.0.10 with pipe_air_gap_receiver_enabled=true and port 9780 exposed, as this allows unauthenticated attackers to trigger heap exhaustion via the unbounded length parameter.

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 IoTDB to version 2.0.10 or disable the AirGap pipe receiver (pipe_air_gap_receiver_enabled=false) if not required.

Recommended fix High confidence

2.0.10

  1. 1. Back up the current IoTDB configuration, data directory, and all custom settings before starting the upgrade
  2. 2. Download Apache IoTDB version 2.0.10 from the official Apache IoTDB download page (https://iotdb.apache.org/Download.html)
  3. 3. Stop the running IoTDB DataNode service gracefully to avoid data corruption
  4. 4. Replace the existing IoTDB installation directory with the new 2.0.10 installation
  5. 5. Restore your backed-up configuration files (iotdb-confignode.properties, iotdb-datanode.properties) into the new installation
  6. 6. Review the release notes for 2.0.10 to check for any required configuration changes or migration steps
  7. 7. Start the IoTDB DataNode service and verify it starts without errors
  8. 8. Confirm that the pipe_air_gap_receiver_enabled setting is either disabled (recommended if not needed) or properly secured with network-level access controls
Caveat Upgrading from IoTDB 1.x to 2.x may involve configuration schema changes, SQL syntax differences, and potential migration requirements; review the 2.0.10 release notes thoroughly before production deployment

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

Have this fixed 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 help mitigating

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-40006 — 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-40006 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