Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-22774 is a high-severity Amplification (CWE-405) vulnerability in Svelte Devalue. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 44th 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 SI-2 (Flaw Remediation) and SC-5 (Denial-of-service Protection) — 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
- 🇪🇺 ENISA EUVD: EUVD-2026-2790
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
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Directly enables application exploitation leading to resource exhaustion DoS via untrusted parse input.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Remediating the flaw by upgrading devalue to version 5.6.2 directly eliminates the typed array hydration vulnerability causing resource exhaustion.
Validating untrusted inputs prior to devalue.parse prevents specially crafted data from triggering excessive CPU or memory consumption in the hydration logic.
Implementing denial-of-service protections limits the impact of resource exhaustion attacks exploiting the vulnerable devalue.parse function.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Resilience mechanisms such as rate limiting and load balancing directly constrain asymmetric resource use.
Capacity planning and monitoring maintain availability headroom against amplification attacks.
Network monitoring detects amplification traffic patterns but does not itself limit asymmetric consumption.
Runtime resource monitoring can surface excessive consumption yet does not enforce authorization or work proofs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Stress-testing and demand-reduction tactics (e.g., bandwidth throttling) blunt amplification vectors that would otherwise let an attacker multiply resource consumption through a single request.