Allocation of Resources Without Limits or Throttling Affecting std/mime/multipart package, versions <1.19.8>=1.20.0-0 <1.20.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-STDMIMEMULTIPART-14552568
- published6 Jan 2026
- disclosed5 Apr 2023
- creditJakob Ackermann
Introduced: 5 Apr 2023
CVE-2023-24536 (opens in a new tab)How to fix?
Upgrade std/mime/multipart to version 1.19.8, 1.20.3 or higher.
Overview
std/mime/multipart is a Go standard library package std/mime/multipart
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling.
Go Vulnerability Report:
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes:
mime/multipart.Reader.ReadFormlimits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.- Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
- ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.
The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use
mime/multipart.Reader.ReadForm, as well as form parsing in thenet/httppackage with the Request methodsFormFile,FormValue,ParseMultipartForm, andPostFormValue.Withfix,ReadFormnow does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.In addition, the fixedmime/multipart.Readerimposes the following limits on the size of parsed forms: - Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable
GODEBUG=multipartmaxparts=. - Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable
GODEBUG=multipartmaxheaders=.