Skip to main content
Menu
CVEs

CVE

Plug denial of service in multipart body parser

CVE-2026-120287EUVD-2026-127132

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

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.20.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.20.4.

Published
Last modified
Reference
Last checked
37/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

Plug, the Elixir web library, has a flaw in its multipart body parser that lets an unauthenticated remote attacker use up a server's memory by sending a request built from parts without headers or from header lines without a name and value. The parser does not count the framing bytes against the configured length limit, so memory use can grow to several times the request size until parsing finishes.

Written by a model from the sources below. Verify against them.

Original description

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.

cve.now Index

37Pcve.now Index 37 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach10/20Affects Hex packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.20.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120287 (Multipart `:length` limit not charged for part and header framing in Plug.Parsers.MULTIPART), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120287 (entry last updated 2026-11-17):
Affected:
- Hex package plug: from 1.13.0, fixed in 1.20.4
- elixir-plug plug: version range not reported
Fixed versions: 1.20.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120287 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120287 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Hex): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/elixir-plug/plug/security/advisories/GHSA-qj4r-jh2r-rw3f
- https://github.com/elixir-plug/plug/commit/497913f2a6d744d693e98e96c5b9c6d88c265695
- https://github.com/elixir-plug/plug/commit/3d3fb645323643935c6c94863c1b3edfd62e2828
- https://cna.erlef.org/cves/CVE-2026-120287.html
- https://osv.dev/vulnerability/EEF-CVE-2026-120287
- https://github.com/elixir-plug/plug/commit/e06acbd3d381931f23cbde7d763136c9ccb091ac
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120287
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120287"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • plugHex

    From 1.13.0 · fixed in 1.20.4

  • elixir-plug/plug

    Version range not reported

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Patch
  3. Repository
  4. Link
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-120287

Is CVE-2026-120287 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120287?

plug (Hex): from 1.13.0 before 1.20.4.Source: cve.now feed data

How do I fix CVE-2026-120287?

Upgrade to a fixed version: 1.20.4.Source: cve.now feed data

More CVEs