Vulnerability in Devalue (CVE-2026-22774)
Summary
Vulnerability in Devalue (CVE-2026-22774). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.6.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-22774 has been found in Devalue.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade Devalue to 5.6.2 or later.
If unsure, ask your IT team or search "Devalue CVE-2026-22774" on the vendor's site.
CVE-2026-22774 (Devalue) — CWE-405 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.6.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-405) exists in Devalue.
Check the vendor advisory for the affected versions of Devalue.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 5.6.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Devalue' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Devalue' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Devalueを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Devalue to 5.6.2ステージング環境で 5.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- report bugzilla.redhat.com
- web github.com
- web security.access.redhat.com