CVE-2026-22775: CWE-405: Asymmetric Resource Consumption (Amplification) in sveltejs devalue
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.
AI Analysis
Technical Summary
The sveltejs devalue library, used for serializing values into strings beyond JSON.stringify capabilities, contains an asymmetric resource consumption vulnerability (CWE-405) in versions 5.1.0 through 5.6.1. The vulnerability occurs because devalue.parse expects base64 encoded strings for ArrayBuffer hydration but does not verify this assumption before decoding. Maliciously crafted inputs can cause excessive CPU and memory usage, potentially resulting in denial of service. The vulnerability is tracked as CVE-2026-22775 with a CVSS 3.1 score of 7.5 (high severity). It is fixed in version 5.6.2. Red Hat advisories confirm the issue and remediation.
Potential Impact
Exploitation of this vulnerability can cause denial of service by consuming excessive CPU time and memory when parsing specially crafted inputs with devalue.parse. There is no impact on confidentiality or integrity reported. The vulnerability affects applications that use devalue.parse on untrusted external data, potentially leading to service disruption.
Mitigation Recommendations
An official fix is available in sveltejs devalue version 5.6.2. Users should upgrade affected versions (>=5.1.0 <=5.6.1) to 5.6.2 or later to remediate this vulnerability. No other mitigation or workaround is indicated by the vendor advisories.
CVE-2026-22775: CWE-405: Asymmetric Resource Consumption (Amplification) in sveltejs devalue
Description
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.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The sveltejs devalue library, used for serializing values into strings beyond JSON.stringify capabilities, contains an asymmetric resource consumption vulnerability (CWE-405) in versions 5.1.0 through 5.6.1. The vulnerability occurs because devalue.parse expects base64 encoded strings for ArrayBuffer hydration but does not verify this assumption before decoding. Maliciously crafted inputs can cause excessive CPU and memory usage, potentially resulting in denial of service. The vulnerability is tracked as CVE-2026-22775 with a CVSS 3.1 score of 7.5 (high severity). It is fixed in version 5.6.2. Red Hat advisories confirm the issue and remediation.
Potential Impact
Exploitation of this vulnerability can cause denial of service by consuming excessive CPU time and memory when parsing specially crafted inputs with devalue.parse. There is no impact on confidentiality or integrity reported. The vulnerability affects applications that use devalue.parse on untrusted external data, potentially leading to service disruption.
Mitigation Recommendations
An official fix is available in sveltejs devalue version 5.6.2. Users should upgrade affected versions (>=5.1.0 <=5.6.1) to 5.6.2 or later to remediate this vulnerability. No other mitigation or workaround is indicated by the vendor advisories.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-09T18:27:19.387Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-22775","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:2926","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:2144","vendor":"Red Hat"}]
Threat ID: 69693b3453752d4047d52868
Added to database: 01/15/2026, 19:08:36 UTC
Last enriched: 07/15/2026, 08:34:51 UTC
Last updated: 09/10/2026, 19:36:52 UTC
Views: 328
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.