CVE-2026-22775: devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse

Published Jan 15, 2026
·
Updated

Summary

Certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input.

Details

The parser's ArrayBuffer hydration logic does not properly validate input before processing. Specially crafted inputs can cause disproportionate memory allocation or CPU usage on the receiving system.

Impact

This is a denial of service vulnerability affecting systems that use devalue.parse to handle data from potentially untrusted sources.

Affected systems should upgrade to patched versions immediately.

Other sources

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.1.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input. This vulnerability is fixed in 5.6.2.

MITRE

Affected Software

3 affected componentsFixes available
npm/devalue>=5.1.0<=5.6.1
npm/devalue>=5.1.0<5.6.2
5.6.2
svelte Devalue Node.js>=5.1.0<5.6.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.6.2
  2. Upgrade

    Upgrade devalue to a version that resolves this vulnerability.

    Fixed in 5.6.2

Event History

Jan 15, 2026
CVE Published
via MITRE·06:59 PM
Data Sourced
via MITRE·06:59 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·08:01 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·10:15 PM
Data Sourced
via GitHub·10:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-22775?

CVE-2026-22775 has been classified as a denial of service vulnerability due to memory or CPU exhaustion.

2

How do I fix CVE-2026-22775?

To address CVE-2026-22775, upgrade devalue to version 5.6.2 or later.

3

What versions are affected by CVE-2026-22775?

CVE-2026-22775 affects devalue versions from 5.1.0 to 5.6.1.

4

What are the potential impacts of CVE-2026-22775?

The potential impacts of CVE-2026-22775 include application crashes and performance degradation due to excessive CPU usage.

5

What is devalue and its role in CVE-2026-22775?

Devalue is a JavaScript library that serializes values, and CVE-2026-22775 exploits its parsing function to cause denial of service.

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