# CVE-2026-65624: Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion

> An unauthenticated remote attacker can exhaust memory in the Cowboy HTTP server by sending duplicate header names, bypassing header count limits.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:** 28 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** AZL-94308, DEBIAN-CVE-2026-65624, EEF-CVE-2026-65624, GHSA-v9x8-262p-f2g5, UBUNTU-CVE-2026-65624

## What is CVE-2026-65624?

CVE-2026-65624 is a medium-severity denial of service vulnerability in ninenines cowboy, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.

The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (", " for regular headers, "; " for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.

The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.

This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

1 open source package ship an affected version, including cowboy.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cowboy` | Hex | From 2.0.0-pre.4 | 2.18.0 |

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

Upgrade cowboy to 2.18.0 or later.

## Is CVE-2026-65624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65624 is a medium-severity denial of service vulnerability in ninenines cowboy, published on 28 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-65624 in the wild and no public exploit code.

Affected packages and fixed versions:
- cowboy (Hex): affected from 2.0.0-pre.4; fixed in 2.18.0

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-65624/ (Markdown: https://insights.sbomify.com/CVE-2026-65624/index.md)
```

## Sources

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

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