CVE-2026-56814

Plug: multipart :length limit is not charged for part headers, enabling unbounded temp-file creation (denial of service)

MEDIUM
6.9
CVSS Score
Published: July 10, 2026 at 11:14 AM UTC
Updated: October 24, 2026 at 11:10 PM UTC
1 product affected across 1 vendorPlug

Using plug by elixir-plug?

Get instant alerts when new vulnerabilities affect plug - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.9
Exploit prediction
EPSS 1%
SSVC
No known exploit

Description

Plug.Parsers.MULTIPART, the multipart request-body parser used to handle file uploads and multipart forms, does not enforce its :length budget against all consumed resources, allowing an unauthenticated remote attacker to cause denial of service. The parser charges the :length limit only for part body bytes; part header bytes are never counted, and a part with an empty body costs zero. Because every part whose Content-Disposition carries a non-empty filename creates a fresh temporary file (via Plug.Upload) and retains a Plug.Upload struct for the duration of the request, an attacker can send a single request composed of many empty-body file parts. Such a request stays well under the configured :length limit (8,000,000 bytes by default) while creating one temporary file per part, leading to inode and disk exhaustion and unbounded memory growth. Any application using Plug.Parsers with the :multipart parser is affected, and no authentication is required, only reachability of a multipart endpoint over HTTP. This vulnerability is associated with program files lib/plug/parsers/multipart.ex and program routines Plug.Parsers.MULTIPART.parse_multipart/2, Plug.Parsers.MULTIPART.parse_multipart_headers/5, Plug.Parsers.MULTIPART.parse_multipart_body/4, and Plug.Parsers.MULTIPART.parse_multipart_file/4. This issue affects plug: from 1.4.0 before 1.16.6, from 1.17.0 before 1.17.4, from 1.18.0 before 1.18.5, from 1.19.0 before 1.19.5, and from 1.20.0 before 1.20.3.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions1.17.01.18.01.19.11.20.01.4.0-rc.0c52b2f32c90bccd718202bafccb5f95594e30183
Affected range stops below 1.16.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.17.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.18.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.19.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.20.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.9MEDIUMEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card