Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22774: CWE-405: Asymmetric Resource Consumption (Amplification) in sveltejs devalue

0
High
VulnerabilityCVE-2026-22774cvecve-2026-22774cwe-405
Published: Thu Jan 15 2026 (01/15/2026, 18:53:21 UTC)
Source: CVE Database V5
Vendor/Project: sveltejs
Product: devalue

Description

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.3.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 typed array hydration expecting an ArrayBuffer as input, but not checking the assumption before creating the typed array. This vulnerability is fixed in 5.6.2.

AI-Powered Analysis

AILast updated: 01/15/2026, 19:15:38 UTC

Technical Analysis

CVE-2026-22774 is a vulnerability classified under CWE-405 (Asymmetric Resource Consumption) found in the sveltejs devalue library, a JavaScript tool used for serializing complex values beyond JSON.stringify capabilities. Versions from 5.3.0 up to 5.6.1 contain a flaw in the devalue.parse function, which is responsible for deserializing strings back into JavaScript values. The vulnerability arises because the function attempts to hydrate typed arrays by assuming the input is an ArrayBuffer without validating this assumption. Maliciously crafted inputs can exploit this by causing the function to allocate excessive memory or consume disproportionate CPU resources, resulting in a denial of service (DoS) condition. This can be triggered remotely without any authentication or user interaction, simply by submitting specially crafted data to an application using the vulnerable devalue.parse. The impact is limited to availability, as confidentiality and integrity are not affected. The vulnerability has a CVSS 3.1 score of 7.5, indicating high severity. The issue was publicly disclosed on January 15, 2026, and fixed in version 5.6.2 of the library. No known exploits have been reported in the wild yet. Organizations using sveltejs devalue in web applications that accept external input should consider this a critical risk for service disruption.

Potential Impact

For European organizations, the primary impact of CVE-2026-22774 is the potential for denial of service attacks against web applications or services that utilize the vulnerable versions of sveltejs devalue to parse untrusted input. This can lead to service outages, degraded performance, and potential loss of availability for end users. Industries relying heavily on web applications with real-time or high-availability requirements, such as financial services, e-commerce, healthcare, and government services, could face operational disruptions. Additionally, organizations providing SaaS or cloud services based in Europe may experience reputational damage and customer trust erosion if their services become unavailable due to exploitation of this vulnerability. While the vulnerability does not directly compromise data confidentiality or integrity, the availability impact alone can have significant business consequences, including regulatory scrutiny under GDPR if service disruptions affect user rights or critical infrastructure. The ease of remote exploitation without authentication increases the risk profile for European entities.

Mitigation Recommendations

The primary mitigation is to upgrade all instances of the sveltejs devalue library to version 5.6.2 or later, where the vulnerability is patched. Organizations should conduct an inventory of applications and services using devalue.parse to identify affected versions. In addition to upgrading, implement strict input validation and sanitization on all external data before it reaches the parsing function to reduce the risk of malicious payloads triggering excessive resource consumption. Employ runtime resource monitoring and rate limiting on endpoints that accept serialized input to detect and throttle abnormal CPU or memory usage patterns indicative of an attack. Consider deploying Web Application Firewalls (WAFs) with custom rules to block suspicious payloads targeting the devalue.parse function. For critical systems, implement redundancy and failover mechanisms to maintain availability in case of DoS attempts. Finally, maintain up-to-date threat intelligence feeds to monitor for emerging exploits targeting this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

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

Threat ID: 69693b3453752d4047d5286d

Added to database: 1/15/2026, 7:08:36 PM

Last enriched: 1/15/2026, 7:15:38 PM

Last updated: 1/15/2026, 8:21:12 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats