CVE-2026-56669: elysiajs elysia · Inefficient Algorithmic Complexity
Affects elysiajs elysiaSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.4.29 soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.29
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade elysia and elysiajs/elysia to 1.4.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| elysiajselysia | Affected
| Fixed in
|
npmelysiajs/elysiapkg:npm/elysiajs/elysiaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to elysia version 1.4.29 or later, where this inefficient algorithmic complexity issue has been fixed. Patch status is confirmed by the version-based fix. No other mitigation is indicated by the vendor advisory.
Description
Elysia v1.4.28 is vulnerable to denial-of-service attacks due to CPU exhaustion in the form data normalization code. Elysia uses `getAll` to retrieve value from FormData. It is called directly relative to the total number of key-value pairs in the form data. The total amount of work the for loop has to do grows quadratically, so doubling the number of unique key-value pairs quadruples the amount of work. In the above PoC, each .getAll call scans through all of the `n` key-value pairs in the form data. Because there are `n` unique keys in the form data, there are .getAll calls, so in total the form data normalizer has to scan `n` x `n` key-value pairs. ### Impact Endpoints using `multipart/form-data` ### Patches 1.4.29 ### Workarounds no 100% confirm workaround beside updating the patch
References
- github.com/elysiajs/elysia/security/advisories/GHSA-9643-4qgh-g8mx (opens in a new tab)
- github.com/elysiajs/elysia/commit/8358ff9efbcedf9534995f5977f26b9ceab59329 (opens in a new tab)
- gist.github.com/jviide/ea040eabe7bac058326174e2cd42dfd9 (opens in a new tab)
- github.com/elysiajs/elysia/releases/tag/1.4.29 (opens in a new tab)