CVE-2026-56669: Elysia: Inefficient Algorithmic Complexity and Interpretation Conflict

Published Jul 8, 2026
·
Updated

Elysia is a Typescript framework for request validation, type inference, OpenAPI documentation, and client-server communication. Prior to 1.4.29, Elysia uses getAll in form data normalization for multipart/form-data endpoints, causing the amount of work to grow quadratically with the number of unique key-value pairs and allowing CPU exhaustion. This issue is fixed in version 1.4.29.

Other sources

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

— GitHub

Affected Software

2 affected componentsFixes available
npm/elysia<1.4.29
npm/elysia<1.4.29
1.4.29

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/elysia to a version that resolves this vulnerability.

    Fixed in 1.4.29
  2. Upgrade

    Upgrade Elysia to a version that resolves this vulnerability.

    Fixed in 1.4.29

Event History

Jul 8, 2026
CVE Published
via MITRE·08:25 PM
Data Sourced
via MITRE·08:25 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Sep 23, 2026
Advisory Published
via GitHub·09:54 PM
Data Sourced
via GitHub·09:54 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-56669?

CVE-2026-56669 has a high severity rating of 7.5.

2

What type of vulnerability is CVE-2026-56669?

CVE-2026-56669 is characterized by inefficient algorithmic complexity that can impact performance.

3

How do I fix CVE-2026-56669?

To fix CVE-2026-56669, update to Elysia version 1.4.29 or later.

4

What software is affected by CVE-2026-56669?

CVE-2026-56669 affects the Elysia framework, which is used for request validation and type inference in TypeScript.

5

What is the impact of CVE-2026-56669?

The impact of CVE-2026-56669 is that it can cause performance degradation under specific conditions due to inefficient handling of multipart/form-data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203