# CVE-2026-40006: Apache IoTDB: Unauthenticated heap-exhaustion DoS via unbounded allocation in IoTDB AirGap pipe receiver

> Unauthenticated attackers can crash Apache IoTDB DataNodes by sending large size values to the AirGap pipe receiver, causing heap exhaustion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-qx9j-cv9x-384r

## What is CVE-2026-40006?

CVE-2026-40006 is a high-severity denial of service vulnerability in Apache IoTDB, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-40006?


## How do I fix CVE-2026-40006?

No fix has been published for CVE-2026-40006 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40006 being exploited?

There is no known exploitation of CVE-2026-40006 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40006 and fix it if it is affected.

What it is: CVE-2026-40006 is a high-severity denial of service vulnerability in Apache IoTDB, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40006 in the wild and no public exploit code.

Affected product: Apache IoTDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40006/ (Markdown: https://insights.sbomify.com/CVE-2026-40006/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40006
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40006
- OSV: https://osv.dev/vulnerability/CVE-2026-40006

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40006/
Summaries are generated and may contain mistakes; the official description above is the record.