# CVE-2026-70616: boringproxy 0.10.0 Resource Exhaustion DoS via GET /loading endpoint

> Authenticated users can exhaust server resources via the /loading endpoint, causing a permanent denial of service for all tunnel traffic.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-5gjj-xq44-85r4

## What is CVE-2026-70616?

CVE-2026-70616 is a high-severity denial of service vulnerability in boringproxy, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

boringproxy through 0.10.0 contains a resource exhaustion vulnerability that allows any authenticated user to permanently exhaust server file descriptors, goroutines, and memory by sending requests to the GET /loading endpoint with attacker-supplied id query parameter values. Because the handler performs no map-lookup validity check and receives on a nil channel that blocks forever, with no timeout, no context cancellation, and no server-side reclamation due to absent HTTP server timeouts, each malicious request permanently holds one goroutine, one file descriptor, and approximately 50 kB of memory until the server's file descriptor limit is reached and listener Accept calls fail, halting all tunnel traffic forwarding for all users.

Weakness: CWE-833 (Deadlock)

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


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

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

## Is CVE-2026-70616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70616 is a high-severity denial of service vulnerability in boringproxy, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70616 exists.

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

## Sources

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

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