Answer in brief
CVE-2026-39825 records a Unknown severity vulnerability in ReverseProxy forwards queries with more than urlmaxqueryparams parameters in net/http/httputil. The current sources do not mark it as known exploited. The current feed maps stdlib (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps stdlib (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| stdlibgo | >=0 <1.25.10 >=1.26.0-0 <1.26.3 | 1.25.10, 1.26.3 |
Published upstream
May 7, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
ReverseProxy can forward queries containing parameters not visible to Rewrite functions. When used with a Rewrite function, or a Director function which parses query parameters, ReverseProxy sanitizes the forwarded request to remove query parameters which are not parsed by url.ParseQuery. ReverseProxy does not take ParseQuery's limit on the total number of query parameters (controlled by GODEBUG=urlmaxqueryparams=N) into account. This can permit ReverseProxy to forward a request containing a query parameter that is not visible to the Rewrite function. For example, the query "a1=x&a2=x&...&a10000=x&hidden=y" can forward the parameter "hidden=y" while hiding it from the proxy's Rewrite function.
Quoted source text, attributed separately from HOL analysis.