CVE-2026-70616
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 10% of all known CVEs.
References
Related Vulnerabilities
Other CWE-833 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-21313 | Medium | 6.5 | 1.6% | - | Fix |
| CVE-2021-1622 | High | 8.6 | 1.0% | - | Fix |
| CVE-2025-1713 | High | 7.5 | 0.7% | - | Fix |
| CVE-2022-43767 | High | 7.5 | 0.7% | - | Fix |
| CVE-2026-44579 | High | 7.5 | 0.7% | - | Fix |
| CVE-2024-8447 | Medium | 5.9 | 0.6% | - | Fix |
Common questions
How do I fix CVE-2026-70616?
No published fix for CVE-2026-70616 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-70616 being actively exploited?
Not that we know of. CVE-2026-70616 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.20% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.
How severe is CVE-2026-70616?
CVE-2026-70616 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-70616
Markdown
[](https://tridentstack.com/cve/CVE-2026-70616)HTML
<a href="https://tridentstack.com/cve/CVE-2026-70616"><img src="https://tridentstack.com/cve/badge/CVE-2026-70616.svg" alt="CVE-2026-70616"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-06.