← Back
CVE-2026-59879
high
CVSS 7.5
Vulnerability in immutable (CVE-2026-59879)
Summary
vulnerability in immutable (CVE-2026-59879). Risk of unauthorized operations or information disclosure. Exploitable via ``set``. Mitigation: upgrade to `5.1.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59879** has been found in immutable.
Attackers can target a specific entry point like ``set`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade immutable to **5.1.8** or later.
If unsure, ask your IT team or search "immutable CVE-2026-59879" on the vendor's site.
CVE-2026-59879 (immutable) — CWE-190 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `set` / `setIn` / `updateIn` / `List`
Patched: `5.1.8` — 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-190) exists in immutable. Attackers reach the vulnerable code path via ``set`` without authentication.
📍 Affected scope
immutable — . Attack surface: `set` / `setIn` / `updateIn` / `List`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.1.8**.
🛡️ 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 'immutable' .` 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 'immutable' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `immutable` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade immutable to 5.1.8ステージング環境で 5.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
immutable
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.8"}]}]
References
- web https://github.com/immutable-js/immutable-js/commit/a1a1ee412dcaa380ab325196283d06594ffe4b84
- web https://github.com/immutable-js/immutable-js/commit/f0bc997d8eb9886aff2236635aa210a95a04304a
- web https://github.com/immutable-js/immutable-js/releases/tag/v4.3.9
- web https://github.com/immutable-js/immutable-js/releases/tag/v5.1.8
- web https://github.com/immutable-js/immutable-js/security/advisories/GHSA-v56q-mh7h-f735
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59879
- web https://github.com/advisories/GHSA-v56q-mh7h-f735