CVE-2026-120287
Received Received - Intake

Memory Exhaustion in Elixir Plug Multipart Parser

Vulnerability report for CVE-2026-120287, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: EEF

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
elixir-plug plug From 1.13.0 (inc) to 1.20.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an Allocation of Resources Without Limits or Throttling vulnerability in the Plug.Parsers.MULTIPART module of the elixir-plug library. An unauthenticated remote attacker can exhaust memory by sending a multipart request with parts lacking headers or containing malformed header lines. The parser only counts header name/value and body bytes against the length limit, ignoring delimiters and separators, allowing memory usage to far exceed expected limits.

Detection Guidance

Monitor memory usage during multipart requests. Use tools like 'htop' or 'ps' to observe Elixir/Erlang process memory growth when handling multipart payloads. Check logs for unusually large requests or failed parsing attempts.

Impact Analysis

This vulnerability can lead to denial of service by consuming excessive memory on the server. Attackers can craft requests that cause the parser process to use 20 to 80 times more memory than the request size, potentially crashing the application or server. Any endpoint using the multipart parser is affected.

Compliance Impact

This vulnerability could lead to denial-of-service conditions by exhausting server memory, which may disrupt services handling sensitive data. For GDPR, this could impact availability of systems processing personal data, potentially violating Article 32 requirements for security and integrity. For HIPAA, service disruptions could affect systems handling protected health information, potentially compromising access controls and integrity as required by the Security Rule.

Mitigation Strategies

Upgrade Plug to version 1.20.4 or later. Alternatively, configure a reverse proxy like nginx to limit request body size. Note that proxy limits may not fully prevent memory exhaustion but reduce risk.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120287. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...