Vulnerability EEF-CVE-2026-56814

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
4 months ago
July 10, 2026 at 11:14 AM UTC
Plug: multipart :length limit is not charged for part headers, enabling unbounded temp-file creation (denial of service)
1.4.0-rc.0 and 1.4.0 - 1.5.0-rc.0 and 1.5.0-rc.1 and 1.5.0-rc.2 and 1.5.0 - 1.18.4 and 1.19.1 - 1.20.2
1.4.0-rc.0 and 1.4.0 - 1.5.0-rc.0 and 1.5.0-rc.1 and 1.5.0-rc.2 and 1.5.0 - 1.18.4 and 1.19.1 - 1.20.2

Summary

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

Details

Summary

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-rc.0 before 1.16.6, from 1.17.0 before 1.17.4, from 1.18.0 before 1.18.5, from 1.19.1 before 1.19.5, and from 1.20.0 before 1.20.3.

Impacted packages

Timeline

Published
4 months ago
July 10, 2026 at 11:14 AM UTC
Fixed (1.20.3)
4 months ago
July 09, 2026 at 09:42 AM UTC
Fixed (1.19.5)
4 months ago
July 09, 2026 at 09:46 AM UTC
Fixed (1.18.5)
4 months ago
July 09, 2026 at 09:50 AM UTC
Fixed (1.17.4)
4 months ago
July 09, 2026 at 09:54 AM UTC
Fixed (1.16.6)
4 months ago
July 09, 2026 at 09:56 AM UTC
Last Modified
2 days ago
November 20, 2026 at 06:15 AM UTC