cve.bz

CVE-2026-56814 elixir-plug plug

6.9 mediumEPSS 1.1%Fix available

Medium (6.9) in elixir-plug plug. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in plug 1.16.6, 1.17.4, 1.18.5.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 66th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • plug (Hex): fixed in 1.16.6, 1.17.4, 1.18.5, 1.19.5, 1.20.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-56814 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56814?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56814?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56814 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
elixir-plug plugfrom 1.4.0-rc.0 before 1.16.6
elixir-plug plugfrom 1.17.0 before 1.17.4
elixir-plug plugfrom 1.18.0 before 1.18.5
elixir-plug plugfrom 1.19.1 before 1.19.5
elixir-plug plugfrom 1.20.0 before 1.20.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-56814Hexplug>=1.4.0-rc.0 <1.16.6
>=1.17.0 <1.17.4
>=1.18.0 <1.18.5
>=1.19.1 <1.19.5
>=1.20.0 <1.20.3
1.16.6, 1.17.4, 1.18.5, 1.19.5, 1.20.3
EEF-CVE-2026-56814v1.20.1, v1.20.0, v1.15.3, v1.17.0, v1.18.1 and 43 moreno fix published

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON