Packages / elysia / Security

HighVulnerabilityGHSA-9643-4qgh-g8mxCVE-2026-56669Published 23 Sep 2026

elysia has Inefficient Algorithmic Complexity and Interpretation Conflict

Your version

Affected releases · elysia

  • 1.x1.0.0 – 1.4.28Fixed in 1.4.29
  • 0.8.x and older0.1.0 – 0.8.17No fix, no longer updated

On 1.x, the newest line:

npm install elysia@1.4.29
Every release on a timeline
1.x
  1. Affected

    1.0.0 – 1.4.28

    132 releases

  2. Fixed

    1.4.29 – 1.4.30

    2 releases, latest

0.x
  1. Affected

    0.1.0 – 0.8.17

    132 releases

266 stable releases of elysia, oldest to newest, one row per major.

What happens

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