Security Resilience

CVE-2026-22774

DoS in Svelte Devalue 5.3.0 – 5.6.2

Published
15 January 2026
Modified
15 July 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0063 49th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-22774 is a high-severity Amplification (CWE-405) vulnerability in Svelte Devalue. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-22774 is a denial-of-service vulnerability in the Svelte devalue JavaScript library, which serializes values into strings beyond the capabilities of JSON.stringify. Versions 5.3.0 through 5.6.1 are affected, where certain inputs to devalue.parse can trigger excessive CPU time or memory consumption. The root cause lies in the typed array hydration logic, which assumes an ArrayBuffer input without validation before creating the typed array, leading to resource exhaustion. This issue, rated at CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and mapped to CWE-405 (Asymmetric Resource Consumption), impacts applications that invoke devalue.parse on untrusted data.

Attackers can exploit this vulnerability remotely without authentication or user interaction by supplying specially crafted inputs to affected applications. Any unauthenticated network attacker targeting a system parsing external data with devalue.parse could induce denial of service through CPU or memory exhaustion, disrupting service availability without compromising confidentiality or integrity.

Mitigation is available via an upgrade to devalue version 5.6.2, which addresses the validation flaw. The Svelte devalue security advisory (GHSA-vw5p-8cq8-m7mv) details the issue, while the release notes and fixing commit (e46afa64dd2b25aa35fb905ba5d20cea63aabbf7) confirm the patch implementation.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-22775Same product: Svelte Devalue
CVE-2026-42570Same product: Svelte Devalue
CVE-2026-30226Same product: Svelte Devalue
CVE-2025-15265Same vendor: Svelte
CVE-2026-42573Same vendor: Svelte
CVE-2026-27902Same vendor: Svelte
CVE-2024-23641Same vendor: Svelte
CVE-2026-27119Same vendor: Svelte
CVE-2026-27121Same vendor: Svelte
CVE-2026-42567Same vendor: Svelte

Affected Assets

svelte
devalue
5.3.0 — 5.6.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-5 directly requires mechanisms to limit the effects of asymmetric resource exhaustion attacks such as amplification DoS.

SC-6 enforces resource quotas and priority allocation that reduce the impact of unauthenticated or low-effort resource requests.

Least-functionality disables unnecessary services or features that could be leveraged for amplification.

SC-7 boundary controls can filter or rate-limit traffic patterns that enable amplification without equivalent client work.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-405, a class-level weakness. Rules are authored against its narrower children: CWE-1050.

References