Skip to content
Noroxi
NVD / CVE Program· CNA Go

CVE-2022-41725: Excessive resource consumption in mime/multipart

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Go standard library mime/multipart 1.19.6, 1.20.1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Go standard library mime/multipart 1.19.6, 1.20.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Feb 28, 2023
Updated
Jun 17, 2026
EPSS
1.2% · 69th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-41725

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
golanggo

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • golang gobefore 1.19.6
  • golang go1.20.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.

  • Go standard library mime/multipart

    • before 1.19.6affected · semver
    • 1.20.0-0 and later · before 1.20.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8aardvark-dnsbefore 2:1.7.0-1.module_el8.9.0+3657+d86e192f2:1.7.0-1.module_el8.9.0+3657+d86e192f
AlmaLinux:8aardvark-dnsbefore 2:1.0.1-38.module_el8.9.0+3627+db8ec1552:1.0.1-38.module_el8.9.0+3627+db8ec155
AlmaLinux:8buildahbefore 1:1.31.3-1.module_el8.9.0+3643+9234dc3b1:1.31.3-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8buildahbefore 1:1.24.6-7.module_el8.9.0+3627+db8ec1551:1.24.6-7.module_el8.9.0+3627+db8ec155
AlmaLinux:8buildah-testsbefore 1:1.24.6-7.module_el8.9.0+3627+db8ec1551:1.24.6-7.module_el8.9.0+3627+db8ec155
AlmaLinux:8buildah-testsbefore 1:1.31.3-1.module_el8.9.0+3643+9234dc3b1:1.31.3-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8cockpit-podmanbefore 75-1.module_el8.9.0+3643+9234dc3b75-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8cockpit-podmanbefore 46-1.module_el8.7.0+3344+5bcd850f46-1.module_el8.7.0+3344+5bcd850f
AlmaLinux:8conmonbefore 3:2.1.8-1.module_el8.9.0+3643+9234dc3b3:2.1.8-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8conmonbefore 2:2.1.4-2.module_el8.9.0+3627+db8ec1552:2.1.4-2.module_el8.9.0+3627+db8ec155
AlmaLinux:8container-selinuxbefore 2:2.205.0-3.module_el8.9.0+3627+db8ec1552:2.205.0-3.module_el8.9.0+3627+db8ec155
AlmaLinux:8container-selinuxbefore 2:2.221.0-1.module_el8.9.0+3643+9234dc3b2:2.221.0-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8containernetworking-pluginsbefore 1:1.1.1-5.module_el8.9.0+3627+db8ec1551:1.1.1-5.module_el8.9.0+3627+db8ec155
AlmaLinux:8containernetworking-pluginsbefore 1:1.3.0-4.module_el8.9.0+3643+9234dc3b1:1.3.0-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8containers-commonbefore 2:1-54.module_el8.9.0+3673+0c64b4032:1-54.module_el8.9.0+3673+0c64b403
AlmaLinux:8containers-commonbefore 2:1-38.module_el8.9.0+3627+db8ec1552:1-38.module_el8.9.0+3627+db8ec155
AlmaLinux:8critbefore 3.18-4.module_el8.9.0+3643+9234dc3b3.18-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8critbefore 3.15-3.module_el8.6.0+3137+d33c3efb3.15-3.module_el8.6.0+3137+d33c3efb
AlmaLinux:8critbefore 3.15-3.module_el8.6.0+2877+8e437bf53.15-3.module_el8.6.0+2877+8e437bf5
AlmaLinux:8criubefore 3.15-3.module_el8.6.0+3137+d33c3efb3.15-3.module_el8.6.0+3137+d33c3efb
AlmaLinux:8criubefore 3.18-4.module_el8.9.0+3643+9234dc3b3.18-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8criubefore 3.15-3.module_el8.6.0+2877+8e437bf53.15-3.module_el8.6.0+2877+8e437bf5
AlmaLinux:8criu-develbefore 3.15-3.module_el8.6.0+2877+8e437bf53.15-3.module_el8.6.0+2877+8e437bf5
AlmaLinux:8criu-develbefore 3.18-4.module_el8.9.0+3643+9234dc3b3.18-4.module_el8.9.0+3643+9234dc3b

+96

Other highest-scoring records for the same primary product.

  • CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only
    54Plan
  • CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and
    52Plan
  • CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-41723Feb 28, 2023 · Denial of service via crafted HTTP/2 stream in net/http and golang.org/x/net
    31Monitor
  • ← EarlierCVE-2022-41724Feb 28, 2023 · Panic on large handshake records in crypto/tls
    30Monitor
  • Later →CVE-2023-24532Mar 8, 2023 · Incorrect calculation on P256 curves in crypto/internal/nistec
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go standard library mime/multipart1.19.6Vendor (CNA)
Go standard library mime/multipart1.20.1Vendor (CNA)
almalinux:delve1.9.1-1.module_el8.8.0+3471+a62632a0 · AlmaLinux:8Package registry (OSV)
almalinux:go-toolset1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang-bin1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang-docs1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang-misc1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang-race1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang-src1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:golang-tests1.19.6-1.module_el8.8.0+3558+75c9cb88 · AlmaLinux:8Package registry (OSV)
almalinux:skopeo2:1.13.3-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:toolbox0.0.99.4-6.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:toolbox-tests0.0.99.4-6.el9_3 · AlmaLinux:9Package registry (OSV)
debian:golang-1.191.19.6-2 · Debian:12Package registry (OSV)
Go:stdlib1.19.6Package registry (OSV)
Go:stdlib1.20.1Package registry (OSV)
opensuse:go1.181.18.10-150000.1.46.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:go1.191.19.7-150000.1.23.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:go1.201.20.2-150000.1.5.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:buildah1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-debuginfo1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-debugsource1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-tests1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-tests-debuginfo1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:golang0:1.19.6-2.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:golang-bin0:1.19.6-2.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:golang-docs0:1.19.6-2.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:golang-misc0:1.19.6-2.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:golang-race0:1.19.6-2.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+18

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records