# CVE-2026-44630: Apache IoTDB: RPC service denial of service via unchecked Thrift string length

> Remote unauthenticated attackers can cause denial of service in Apache IoTDB by sending crafted Thrift frames that trigger excessive memory allocation.

- **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 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-q69g-x875-pprm

## What is CVE-2026-44630?

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

### Official description

Improper validation of length fields in the Apache IoTDB RPC service may allow a remote unauthenticated attacker to cause a denial of service. By sending a crafted malformed Thrift frame, an attacker can cause IoTDB to allocate an excessive amount of memory and crash with an OutOfMemoryError.

This issue affects Apache IoTDB: before 1.3.8, from 2.0.0 before 2.0.9.

Users are recommended to upgrade to version 2.0.10, which fixes the issue.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-44630 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44630 is a high-severity denial of service vulnerability in Apache IoTDB, published on 10 Aug 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-44630 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-44630/ (Markdown: https://insights.sbomify.com/CVE-2026-44630/index.md)
```

## Sources

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

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