CVE-2026-46625

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

JavaScript Cookie is a JavaScript API for handling cookies, client-side. Prior to version 3.0.7, js-cookie's internal assign() helper copies properties with for...in + plain assignment. When the source object is produced by JSON.parse, the JSON object's "__proto__" member is an own enumerable property, so the for…in enumerates it and the target[key] = source[key] write triggers the Object.prototype.__proto__ setter on the fresh target ({}). The result is a per-instance prototype hijack: Object.prototype itself is untouched, but the merged attributes object now inherits attacker-controlled keys. Because the consuming set() function then enumerates the merged object with another for...in, every key the attacker placed on the polluted prototype lands in the resulting Set-Cookie string as an attribute pair. The attacker can set domain=, secure=, samesite=, expires=, and path= on cookies whose attributes the developer thought were locked down. This issue has been patched in version 3.0.7.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
59%
KEV
Not listed

Published

May 21, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Jun 11, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Per-instance prototype hijack in assign() enables cookie-attribute injection · Advisory · js-cookie/js-cookie · GitHub

https://github.com/js-cookie/js-cookie/security/advisories/GHSA-qjx8-664m-686j
github_release Patch Available

v3.0.7

Patch available: js-cookie/js-cookie v3.0.7

https://github.com/js-cookie/js-cookie/releases/tag/v3.0.7
github_commit Patch Available

commit eb3c40e89731 (js-cookie/js-cookie)

Patch available: js-cookie/js-cookie v3.0.7 (contains commit eb3c40e89731)

https://github.com/js-cookie/js-cookie/commit/eb3c40e89731e99b8970faaf35ddad249c6c0020

Patch Availability(10)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-js-cookie2.2.1-1 ... 3.0.7+~3.0.6-2 (8 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-js-cookie3.0.1+~3.0.0-3, 3.0.7+~3.0.6-1, 3.0.7+~3.0.6-2, 3.0.8+~3.0.6-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-js-cookie3.0.1+~3.0.0-3, 3.0.7+~3.0.6-1, 3.0.7+~3.0.6-2, 3.0.8+~3.0.6-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-js-cookie3.0.1+~3.0.0-33.0.7+~3.0.6-1
npm(1)
PackageVulnerable rangeFixed inDependents
js-cookie3.0.7

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 203 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-09 13:41 UTCEG score recompute
  11. 2026-09-09 13:41 UTCVendor advisory
  12. 2026-09-09 12:39 UTCEG score recompute
  13. 2026-09-09 12:39 UTCVendor advisory
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-07 13:53 UTCEG score recompute
  17. 2026-09-07 13:53 UTCVendor advisory
  18. 2026-09-07 12:41 UTCEG score recompute
  19. 2026-09-07 12:41 UTCVendor advisory
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-04 13:29 UTCEG score recompute
  22. 2026-09-04 13:29 UTCVendor advisory
  23. 2026-09-04 12:22 UTCEG score recompute
  24. 2026-09-04 12:22 UTCVendor advisory
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 12:21 UTCEG score recompute
  4. 2026-09-01 12:21 UTCVendor advisory
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:41 UTCEPSS rescore
  8. 2026-08-28 16:47 UTCEG score recompute
  9. 2026-08-28 16:47 UTCVendor advisory
  10. 2026-08-28 16:00 UTCEG score recompute
  11. 2026-08-28 16:00 UTCVendor advisory
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 20:44 UTCVendor advisory
  14. 2026-08-26 16:24 UTCEG score recompute
  15. 2026-08-26 16:24 UTCVendor advisory
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-26 12:21 UTCEG score recompute
  18. 2026-08-26 12:21 UTCVendor advisory
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 13:24 UTCEG score recompute
  21. 2026-08-25 13:24 UTCVendor advisory
  22. 2026-08-25 12:20 UTCEG score recompute
  23. 2026-08-25 12:20 UTCVendor advisory
  24. 2026-08-23 16:46 UTCEG score recompute
  25. 2026-08-23 16:46 UTCVendor advisory
  26. 2026-08-23 00:19 UTCEPSS rescore
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 21:44 UTCEG score recompute
  29. 2026-08-21 21:44 UTCVendor advisory
  30. 2026-08-20 22:55 UTCEPSS rescore
  31. 2026-08-20 18:42 UTCEG score recompute
  32. 2026-08-20 18:42 UTCVendor advisory
  33. 2026-08-19 17:04 UTCEPSS rescore
  34. 2026-08-19 12:27 UTCEG score recompute
  35. 2026-08-19 12:27 UTCVendor advisory
  36. 2026-08-19 12:11 UTCEG score recompute
  37. 2026-08-19 12:11 UTCVendor advisory
  38. 2026-08-18 13:48 UTCEPSS rescore
  39. 2026-08-17 13:47 UTCEPSS rescore
  40. 2026-08-17 09:46 UTCVendor advisory
  41. 2026-08-16 16:49 UTCEG score recompute
  42. 2026-08-16 16:49 UTCVendor advisory
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 03:22 UTCEG score recompute
  45. 2026-08-16 03:22 UTCVendor advisory
  46. 2026-08-16 02:14 UTCEPSS rescore
  47. 2026-08-15 03:12 UTCEG score recompute
  48. 2026-08-15 03:12 UTCVendor advisory
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 14:14 UTCVendor advisory
  51. 2026-08-14 01:55 UTCEG score recompute
  52. 2026-08-14 01:55 UTCVendor advisory
  53. 2026-08-13 22:00 UTCEPSS rescore
  54. 2026-08-13 12:28 UTCEG score recompute
  55. 2026-08-13 12:28 UTCVendor advisory
  56. 2026-08-13 02:32 UTCVendor advisory
  57. 2026-08-12 14:13 UTCEG score recompute
  58. 2026-08-12 14:13 UTCVendor advisory
  59. 2026-08-12 13:51 UTCEPSS rescore
  60. 2026-08-12 01:42 UTCEG score recompute
  61. 2026-08-12 01:42 UTCVendor advisory
  62. 2026-08-11 13:23 UTCEG score recompute
  63. 2026-08-11 13:23 UTCVendor advisory
  64. 2026-08-11 12:23 UTCEG score recompute
  65. 2026-08-11 12:23 UTCVendor advisory
  66. 2026-08-11 01:43 UTCEG score recompute
  67. 2026-08-11 01:43 UTCVendor advisory
  68. 2026-08-11 00:00 UTCEPSS rescore
  69. 2026-08-10 13:23 UTCEG score recompute
  70. 2026-08-10 13:23 UTCVendor advisory
  71. 2026-08-10 12:26 UTCEG score recompute
  72. 2026-08-10 12:26 UTCVendor advisory
  73. 2026-08-10 02:03 UTCEG score recompute
  74. 2026-08-10 02:03 UTCVendor advisory
  75. 2026-08-09 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46625?
CVE-2026-46625 is a high vulnerability published on May 21, 2026. JavaScript Cookie is a JavaScript API for handling cookies, client-side. Prior to version 3.0.7, js-cookie's internal assign() helper copies properties with for...in + plain assignment. When the source object is produced by JSON.parse, the JSON object's "proto" member is an own enumerable property,…
When was CVE-2026-46625 disclosed?
CVE-2026-46625 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46625 actively exploited?
CVE-2026-46625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.3% of all scored CVEs.
What is the CVSS score of CVE-2026-46625?
CVE-2026-46625 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46625, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46625

Explore →

Is Your Infrastructure Affected by CVE-2026-46625?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.