← Back
CVE-2026-42570
high
CVSS 7.5
Vulnerability in devalue (CVE-2026-42570)
Summary
vulnerability in devalue (CVE-2026-42570). Risk of unauthorized operations or information disclosure. Exploitable via ``devalue.parse``. Mitigation: upgrade to `5.8.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42570** has been found in devalue.
Attackers can target a specific entry point like ``devalue.parse`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade devalue to **5.8.1** or later.
If unsure, ask your IT team or search "devalue CVE-2026-42570" on the vendor's site.
CVE-2026-42570 (devalue) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `devalue.parse`
Patched: `5.8.1` — 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.
❓ What is the problem
**A vulnerability** (CWE-770) exists in devalue. Attackers reach the vulnerable code path via ``devalue.parse`` without authentication.
📍 Affected scope
devalue — . Attack surface: `devalue.parse`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.8.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade devalue to 5.8.1ステージング環境で 5.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
devalue
[{"type":"SEMVER","events":[{"introduced":"5.6.3"},{"fixed":"5.8.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42570
- package https://github.com/sveltejs/devalue
- patch [email protected]
- patch [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-77vg-94rm-hx3p
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c