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
CVE-2026-22774 can let an unauthenticated remote sender make affected applications consume excessive CPU or memory, causing denial of service. The risk applies when applications use Svelte devalue.parse on data supplied by outsiders. The vulnerable devalue range is 5.3.0 through 5.6.1, and the source bundle states it is fixed in 5.6.2.
Executive priority
Treat as a high-priority availability risk for internet-facing or API-driven services using devalue.parse. It does not indicate data theft or code execution, but service disruption may be possible without authentication. Patch affected applications during the next urgent maintenance window.
Technical view
Svelte devalue versions >=5.3.0 and <5.6.2 mishandle certain inputs in devalue.parse. The typed array hydration path expects an ArrayBuffer but does not verify that assumption before creating the typed array, enabling CPU and/or memory exhaustion. CVSS 3.1 is 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Likely exposure
Exposure is likely in JavaScript or Node.js applications that depend on devalue 5.3.0 to 5.6.1 and call devalue.parse on externally supplied data. Internal-only parsing or versions 5.6.2 and later are less likely to be exposed based on provided sources.
Exploitation context
The CVSS vector indicates remote, low-complexity, unauthenticated exploitation with no user interaction. The impact is availability only. The bundle does not indicate CISA KEV listing or active exploitation, so active exploitation should not be assumed.
Researcher notes
Focus review on typed array hydration behavior and whether application-controlled data reaches devalue.parse. The public advisory and fix identify missing type validation before typed array creation. Do not infer broader Svelte framework exposure unless devalue.parse and vulnerable versions are present.
Mitigation direction
Upgrade sveltejs devalue to version 5.6.2 or later.
Prioritize services parsing externally supplied data with devalue.parse.
Review Red Hat errata if using affected Red Hat-distributed packages.
If immediate upgrade is blocked, follow vendor guidance and reduce untrusted parsing exposure.
Validation and detection
Inventory direct and transitive devalue dependencies in application manifests and lockfiles.
Confirm deployed versions are not >=5.3.0 and <5.6.2.
Identify code paths calling devalue.parse on external input.
Verify production builds include the upgraded dependency version.
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.