CVE-2026-81176: Svelte devalue: DoS via malformed input

Published Sep 16, 2026
·
Updated

Impact

devalue.parse prior to version 5.9.2 fails to reject out-of-bounds indices. Specially-crafted payloads can exploit this to cause devalue to alternate between different array representations, resulting in work that is quadratic with payload size.

Applications are potentially affected if they call devalue.parse with untrusted data.

Patches

The bug is fixed in devalue@5.9.2.

Other sources

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. Prior to 5.9.2, devalue.parse does not reject out-of-bounds indices that are greater than or equal to values.length in src/parse.js. A specially crafted untrusted payload can make the parser alternate between array representations, producing quadratic work as the payload grows and causing denial of service in applications that parse untrusted devalue data. This issue is fixed in version 5.9.2.

— MITRE

Affected Software

2 affected componentsFixes available
npm/devalue<5.9.2
npm/devalue<5.9.1
5.9.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.9.2
  2. Upgrade

    Upgrade devalue to a version that resolves this vulnerability.

    Fixed in 5.9.2

Event History

Sep 16, 2026
CVE Published
via MITRE·06:34 PM
Data Sourced
via MITRE·06:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Sep 17, 2026
Advisory Published
via GitHub·08:28 PM
Data Sourced
via GitHub·08:28 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which applications are exposed to this denial-of-service issue?

Applications using devalue versions prior to 5.9.2 are exposed if they call devalue.parse on untrusted devalue data. The impact is denial of service through excessive parser work.

2

What does an attacker need to exploit the issue?

An attacker needs to supply a specially crafted untrusted payload that reaches devalue.parse. No privileges or user interaction are required according to the provided severity vector.

3

Are applications affected merely by installing devalue?

The described vulnerable condition is parsing untrusted devalue data with devalue.parse. The data does not establish that applications which never parse untrusted input are affected.

4

What is the remediation?

Upgrade devalue to version 5.9.2, which fixes the handling of out-of-bounds indices. If an immediate upgrade is not possible, avoid passing untrusted payloads to devalue.parse.

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