CVE-2026-120287 json
Multipart `:length` limit not charged for part and header framing in Plug.Parsers.MULTIPART
published 19h ago modified 17h ago also EEF-CVE-2026-120287 , EUVD-2026-127132 , GHSA-qj4r-jh2r-rw3f
- cvss
- 6.9
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Allocation of Resources Without Limits or Throttling vulnerability in Plug.Parsers.MULTIPART in elixir-plug plug allows an unauthenticated remote attacker to exhaust memory via a multipart request body built from parts without headers, or from header lines without a name and a value. The parser charges the :length limit only with the name and value bytes of each part header and the bytes of each part body. The part delimiter, the header separator, and the line endings cost nothing.
In lib/plug/parsers/multipart.ex, Plug.Parsers.MULTIPART.parse_multipart_headers/5 keeps an entry for every part without a content-disposition header, together with its header list, until the whole body is read. A request made of such parts does not reach the limit at any size, and the parser process holds a multiple of the request size in memory until parsing completes. Any endpoint that uses Plug.Parsers with the :multipart parser is reachable.
This issue affects plug: from 1.13.0 before 1.20.4.
Patch / fix
- hex plug 1.20.4
- elixir-plug plug 1.20.4
Is CVE-2026-120287 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 17h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | plug | >=1.13.0, <1.20.4 |
1.20.4 |
Affected products
- elixir-plug plug
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/elixir-plug/plug/commit/e06acbd3d381931f23cbde7d763136c9ccb091ac
related, web
-
github.com
/elixir-plug/plug/commit/497913f2a6d744d693e98e96c5b9c6d88c265695
patch
-
github.com
/elixir-plug/plug/commit/3d3fb645323643935c6c94863c1b3edfd62e2828
patch
-
github.com
/elixir-plug/plug/security/advisories/GHSA-qj4r-jh2r-rw3f
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-120287.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-120287
related
-
hex.pm
/packages/plug
package
Sources
- CVE List CVE-2026-120287
- NVD CVE-2026-120287
- OSV EEF-CVE-2026-120287
- Maintainer advisory GHSA-qj4r-jh2r-rw3f
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of elixir-plug/plug published their own advisory on GitHub. Reviewed sources take precedence over it.