# CVE-2026-69664: httpd parks a request worker indefinitely on a malformed chunk size sent after the headers

> Unauthenticated remote attackers can cause denial of service in Erlang OTP httpd by sending malformed chunked requests that permanently occupy worker threads.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** AZL-98466, DEBIAN-CVE-2026-69664, EEF-CVE-2026-69664, GHSA-mr35-8h7w-w3gq, UBUNTU-CVE-2026-69664

## What is CVE-2026-69664?

CVE-2026-69664 is a high-severity denial of service vulnerability in Erlang OTP, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Release of Resource after Effective Lifetime vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by sending a request with a chunked body whose chunk-size line is not a hexadecimal number. The worker serving the connection is never released and no timeout reclaims it, so repeating the request across connections occupies every available worker and denies service to legitimate clients. No authentication is required and the default configuration is affected.

The chunk-size line must arrive in a write separate from the headers. When the body accompanies the headers, httpd_request_handler:handle_body/3 calls http_chunk:decode/3 inside a try ... catch throw:Error, so the {error, {chunk_size, _}} thrown by http_chunk:decode_size/4 is answered with 400 Bad Request. When the chunk size arrives later, the decoder is resumed through a bare catch in httpd_request_handler:handle_info/2, which converts the throw into a return value rather than raising it; the resulting error tuple is then treated as the next decoder continuation, the socket is re-armed, and the worker waits for data that never comes. The request timeout has already been cancelled at the point the headers were accepted, and the periodic byte-rate check is only armed when minimum_bytes_per_second is configured, which it is not by default.

This issue affects OTP from OTP 18.1.4 before OTP 27.3.4.17, OTP 28.5.0.6, and OTP 29.0.6, corresponding to inets from 6.0.3 before 9.3.2.7, 9.6.2.3, and 9.7.2.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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


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

Upgrade to a fixed version.

## Is CVE-2026-69664 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69664 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69664 is a high-severity denial of service vulnerability in Erlang OTP, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69664 exists.

Affected product: Erlang OTP. 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-69664/ (Markdown: https://insights.sbomify.com/CVE-2026-69664/index.md)
```

## Sources

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

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