← Back
CVE-2026-46625
high
CVSS 7.5
Vulnerability in js-cookie (CVE-2026-46625)
Summary
vulnerability in js-cookie (CVE-2026-46625). Data can be tampered with by attackers. Exploitable via ``for...in``. Mitigation: upgrade to `3.0.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46625** has been found in js-cookie.
Attackers can target a specific entry point like ``for...in`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade js-cookie to **3.0.7** or later.
If unsure, ask your IT team or search "js-cookie CVE-2026-46625" on the vendor's site.
CVE-2026-46625 (js-cookie) — CWE-1321 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `for...in` / `JSON.parse` / `Object.prototype.__proto__` / `target`
Patched: `3.0.7` — 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-1321) exists in js-cookie. Attackers reach the vulnerable code path via ``for...in`` without authentication.
📍 Affected scope
js-cookie — . Attack surface: `for...in` / `JSON.parse` / `Object.prototype.__proto__` / `target`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **3.0.7**.
🛡️ 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 'js-cookie' .` 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 'js-cookie' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `js-cookie` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade js-cookie to 3.0.7ステージング環境で 3.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
js-cookie
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.0.7"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-46625
- package https://github.com/js-cookie/js-cookie
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/advisories/GHSA-qjx8-664m-686j
- web [email protected]
- web [email protected]
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c