Memory exhaustion in query parameter parsing in net/url
The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-61726US | — | — | ||
The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum reques… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:10096WEB
- https://access.redhat.com/errata/RHSA-2026:10104WEB
- https://access.redhat.com/errata/RHSA-2026:10184WEB
- https://access.redhat.com/errata/RHSA-2026:10225WEB
- https://access.redhat.com/errata/RHSA-2026:10250WEB
- https://access.redhat.com/errata/RHSA-2026:11408WEB
- https://access.redhat.com/errata/RHSA-2026:11414WEB
- https://access.redhat.com/errata/RHSA-2026:11747WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan