CVE-2026-54892 json
Plug: quadratic-time decoding of nested query/body parameters enables denial of service
published 2026-06-23 4 mo ago modified 2026-10-25 14 d ago also EEF-CVE-2026-54892 , GHSA-j43x-5hjq-rgxf , EUVD-2026-38446
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
Inefficient algorithmic complexity in Plug's nested-parameter decoder allows an unauthenticated remote attacker to cause denial of service. Plug.Conn.Query.decode/4 (and Plug.Conn.Query.decode_each/2) parse query strings and application/x-www-form-urlencoded request bodies. When a key contains many bracketed segments such as a[a][a][a]=1, the decoder walks the brackets and, for each of the N levels, performs a map operation keyed on an ever-growing binary prefix of the key, hashing the full byte range at each step. The total decode cost is therefore quadratic in the number of nesting levels.
With the default Plug.Parsers.URLENCODED body limit of 1,000,000 bytes, a single request can carry roughly 333,000 nesting levels and saturate a BEAM scheduler for minutes. A small number of concurrent requests can saturate all schedulers and render a Plug-based server unresponsive. No authentication or knowledge of application routes is required.
This vulnerability is associated with program files lib/plug/conn/query.ex and program routines Plug.Conn.Query.decode/4, Plug.Conn.Query.decode_each/2, Plug.Conn.Query.split_keys/6, Plug.Conn.Query.insert_keys/3, and Plug.Conn.Query.finalize_pointer/2.
This issue affects plug from 1.15.0 before 1.15.5, 1.16.4, 1.17.2, 1.18.3, and 1.19.3.
Patch / fix
- hex plug 1.15.5, 1.16.4, 1.17.2, 1.18.3, 1.19.3
- elixir-plug plug 1.15.5, 1.16.4, 1.17.2, 1.18.3, 1.19.3
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/elixir-plug/plug/security/advisories/GHSA-j43x-5hjq-rgxf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | plug | >=1.15.0, <1.15.5 >=1.16.0, <1.16.4 >=1.17.0, <1.17.2 >=1.18.0, <1.18.3 >=1.19.0, <1.19.3 |
1.15.5 1.16.4 1.17.2 1.18.3 1.19.3 |
Affected products
- elixir-plug plug
Classification
- Weakness
-
- CWE-407 Inefficient Algorithmic Complexity
References
-
github.com
/elixir-plug/plug/commit/c317d08fdcf96e17931f7419275b2b8c4bf3e951
patch, web
-
github.com
/elixir-plug/plug/commit/9c5d37c440eaae92869eed7c014c47266744fadb
patch, web
-
github.com
/elixir-plug/plug/commit/d737eb236f17e31a36290e39f9ef3cd86a1343bd
patch, web
-
github.com
/elixir-plug/plug/commit/d4e5568392a4b29e545b91e12e87d6098f976145
patch, web
-
github.com
/elixir-plug/plug/commit/a61124aa625d819a218fb07f90afbac8aa85eb0e
patch, web
-
github.com
/elixir-plug/plug/security/advisories/GHSA-j43x-5hjq-rgxf
vendor-advisory, related, exploit, web, advisory
-
cna.erlef.org
/cves/CVE-2026-54892.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-54892
related, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-54892
advisory
-
github.com
/elixir-plug/plug
package
-
github.com
/elixir-plug/plug/blob/v1.19.3/CHANGELOG.md#v1193-2026-06-23
web
-
hex.pm
/packages/plug
package
Sources
- CVE List CVE-2026-54892
- GitHub Advisory GHSA-j43x-5hjq-rgxf
- NVD CVE-2026-54892
- OSV EEF-CVE-2026-54892
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.