Back to CVE records
Medium 6.5Published Aug 5, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects boringproxy. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.5 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-833
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
VulnCheck
NVD analysis
Deferred
Record last updated
Aug 6, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
boringproxy boringproxy
boringproxy:boringproxy (from the name)
through 0.10.0
CNA record

References

  • technical-description, exploit
  • third-party-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.