# CVE-2026-116011: Crow before 1.3.4 Denial of Service via Deeply Nested JSON in crow::json::load()


- **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
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-7x84-xhp8-6cqj, GHSA-88wj-6c62-8f7x

## What is CVE-2026-116011?

CVE-2026-116011 is a high-severity vulnerability in CrowCpp Crow, published on 24 Oct 2026. 

### Official description

Crow before 1.3.4 contains an uncontrolled recursion vulnerability in crow::json::load() that allows remote unauthenticated attackers to crash the server by sending deeply nested JSON. Attackers can send a request body with thousands of nested objects to exhaust the worker thread stack, terminating the process and dropping all connections.

Weakness: CWE-674 (Uncontrolled Recursion)

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


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

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

## Is CVE-2026-116011 being exploited?

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

Public exploit code:

- A remote denial of service vulnerability in CrowCPP due to uncontrolled recursion. (github_poc): https://github.com/D7EAD/CVE-2026-116011

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116011 is a high-severity vulnerability in CrowCpp Crow, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116011 in the wild and no public exploit code.

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

## Sources

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

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