You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[GHSA-m5pj-3536-3xcp] - [v1] - /fetch proxy has no size cap on the proxied response body (memory-exhaustion DoS) #2781
The v1 proxy's /fetch route read the upstream response body with no size cap, so a remote server could exhaust the proxy's memory with an oversized response. The advisory holds the full report.
This issue tracks the v1 line. The advisory's draft card was converted into the v2 issue, #2780, so this one was filed separately for board #11.
Activity
cliffhall commentedon Oct 22, 2026
Shipped in 1.0.3, published to npm under
v1-latest. Advisory: GHSA-m5pj-3536-3xcp.Landed on
v1/mainin merge commite9cd45b9, together with GHSA-wmjf-2m46-2352 (#2756). The fix commits:7e6c03dcfix(server): cap the /fetch response body5542ab8cfix(server): decode the capped /fetch body like response.text()ccb8a3adtest(server): drive the /fetch route's body cap end to endThe v2 half is #2780 and shipped in 2.12.0.