CVE-2026-70616

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.5
EG Score
6.5(high)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

boringproxy 0.10.0 Resource Exhaustion DoS via GET /loading endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/boringproxy-resource-exhaustion-dos-via-get-loading-endpoint
generic🟡 PoC Available

Denial-Of-Service-Through-Unbounded-Resource-Consumption-In-Request-Handler-boringproxy-/README.md at master · theopaid/Denial-Of-Service-Through-Unbounded-Resource-Consumption-In-Request-Handler-boringproxy- · GitHub

https://github.com/theopaid/Denial-Of-Service-Through-Unbounded-Resource-Consumption-In-Request-Handler-boringproxy-/blob/master/README.md

Vendor Advisories for CVE-2026-70616(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:38 UTCEG score recompute
  2. 2026-08-21 02:38 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 00:28 UTCEG score recompute
  5. 2026-08-20 00:28 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 22:17 UTCEG score recompute
  8. 2026-08-18 22:17 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-17 20:08 UTCEG score recompute
  12. 2026-08-17 20:07 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 17:53 UTCEG score recompute
  15. 2026-08-16 17:53 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 15:43 UTCEG score recompute
  20. 2026-08-15 15:43 UTCGHSA enrichment
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-14 13:33 UTCEG score recompute
  23. 2026-08-14 13:33 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 11:23 UTCEG score recompute
Show 21 more
  1. 2026-08-13 11:23 UTCGHSA enrichment
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-12 09:13 UTCEG score recompute
  4. 2026-08-12 09:13 UTCGHSA enrichment
  5. 2026-08-11 07:03 UTCEG score recompute
  6. 2026-08-11 07:03 UTCGHSA enrichment
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-10 04:53 UTCEG score recompute
  9. 2026-08-10 04:53 UTCGHSA enrichment
  10. 2026-08-09 13:47 UTCEPSS rescore
  11. 2026-08-09 02:44 UTCEG score recompute
  12. 2026-08-09 02:44 UTCGHSA enrichment
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-08 00:34 UTCEG score recompute
  15. 2026-08-08 00:34 UTCGHSA enrichment
  16. 2026-08-06 22:24 UTCEG score recompute
  17. 2026-08-06 22:24 UTCGHSA enrichment
  18. 2026-08-06 13:47 UTCEPSS rescore
  19. 2026-08-05 20:32 UTCEG score recompute
  20. 2026-08-05 20:15 UTCEG score recompute
  21. 2026-08-05 20:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-70616?
CVE-2026-70616 is a medium vulnerability published on August 5, 2026. 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…
When was CVE-2026-70616 disclosed?
CVE-2026-70616 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70616 actively exploited?
CVE-2026-70616 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.0% of all scored CVEs.
What is the CVSS score of CVE-2026-70616?
CVE-2026-70616 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-70616?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70616, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-70616

Explore →

Is Your Infrastructure Affected by CVE-2026-70616?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.