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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-70616 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70616 exists.
Sources
Also known as GHSA-5gjj-xq44-85r4.