CVE-2026-22774: devalue vulnerable to denial of service due to memory exhaustion in devalue.parse
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.
Security readout for executives and security teams
Plain-English summary
This is a denial-of-service issue in Svelte’s devalue library. If an application uses vulnerable devalue.parse on externally supplied data, crafted input can make the process spend excessive CPU or memory, potentially disrupting the service. The fix is devalue 5.6.2.
Executive priority
Prioritize remediation for internet-facing or partner-facing services using devalue.parse on user-controlled data. Internal-only use without untrusted parsing is lower urgency but should still be upgraded during normal dependency maintenance.
Technical view
devalue versions 5.3.0 through 5.6.1 can exhaust CPU or memory during devalue.parse. The root cause is typed array hydration assuming an ArrayBuffer without validating that assumption before typed array creation. Impact is availability only, with CVSS 7.5 AV:N/AC:L/PR:N/UI:N.
Likely exposure
Exposure is limited to applications that include sveltejs devalue >=5.3.0 and <5.6.2 and call devalue.parse on externally supplied or otherwise untrusted data.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation appears network-reachable only when an application exposes a path that feeds attacker-controlled input into devalue.parse.
Researcher notes
The vulnerable condition is specific to parse-time typed array hydration and unchecked ArrayBuffer assumptions. The public bundle identifies the affected range, fixed release, commit, CVSS vector, and Red Hat references, but does not provide evidence of active exploitation.
Mitigation direction
Upgrade devalue to version 5.6.2 or later.
Review lockfiles and transitive dependencies for vulnerable devalue versions.
Avoid parsing externally supplied devalue data until upgraded.
Apply relevant downstream vendor advisories where devalue is packaged.
Use request size and rate limits on parsing endpoints.
Validation and detection
Confirm resolved devalue version is 5.6.2 or later.
Identify all code paths that invoke devalue.parse.
Verify whether those paths accept external or untrusted input.
Review service metrics for parsing-related CPU or memory spikes.
Check Red Hat advisory applicability for affected packaged products.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-405: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-405 · source CWE mapping
Asymmetric Resource Consumption (Amplification)
Asymmetric Resource Consumption (Amplification) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.