# CVE-2026-72752: Routinator exits when requesting the output repeatedly


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-9hhm-hxh6-hwxr

## What is CVE-2026-72752?

CVE-2026-72752 is a medium-severity vulnerability in NLnet Labs Routinator, published on 26 Oct 2026. 

### Official description

Routinator runs out of memory when the JSON output is requested many times concurrently. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP server. Additionally Routinator runs into a stack overflow and exits when a payload item with too much metadata is discarded at once.

This only affects users that make their HTTP or RTR server available to untrusted networks.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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


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

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

## Is CVE-2026-72752 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72752 is a medium-severity vulnerability in NLnet Labs Routinator, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-72752 in the wild and no public exploit code.

Affected product: NLnet Labs Routinator. 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-72752/ (Markdown: https://insights.sbomify.com/CVE-2026-72752/index.md)
```

## Sources

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

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