Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-22775 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 Network Denial of Service (T1498); 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 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-22775 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.1.0 through 5.6.1 are affected, where certain inputs to devalue.parse can trigger excessive CPU time and memory consumption. The root cause lies in the ArrayBuffer hydration logic, which assumes base64-encoded string input without validation prior to decoding, impacting applications that process externally supplied data with devalue.parse. The vulnerability carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and is classified under CWE-405 (Asymmetric Resource Consumption, or resource exhaustion).
Attackers can exploit this vulnerability remotely without authentication or user interaction by providing specially crafted inputs to any application endpoint that invokes devalue.parse on untrusted data. Successful exploitation leads to resource exhaustion, causing denial of service through high CPU and memory usage on the targeted system. No privileges are required, making it accessible to unauthenticated network adversaries.
Mitigation is available in devalue version 5.6.2, which addresses the issue via a fix detailed in the project's GitHub commit (11755849fa0634ae294a15ec0aef2f43efcad7c4), release notes (v5.6.2), and security advisory (GHSA-g2pg-6438-jwpf). Security practitioners should upgrade affected applications to the patched version and audit usage of devalue.parse with untrusted inputs.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-2680
Vulnerability Data
Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.1.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 ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input. This vulnerability is fixed in 5.6.2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 3 OS baselines
—
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.
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.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248553 OL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-405
- V-248552 OL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-405
Oracle Linux 9 (2 rules)
- V-271709 OL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-405
- V-271710 OL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-405
RHEL 8 (2 rules)
- V-230244 RHEL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-405
- V-244525 RHEL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-405