CVE-2017-5941

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2018-07-18. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 61%
CISA-KEV: Not listedEPSS: 61%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in the node-serialize package 0.0.4 for Node.js. Untrusted data passed into the unserialize() function can be exploited to achieve arbitrary code execution by passing a JavaScript Object with an Immediately Invoked Function Expression (IIFE).

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.0%
KEV
Not listed

Published

February 9, 2017

Last Modified

May 13, 2026

Advisory Details (2)

Auto-updated May 17, 2026
No patch confirmed yet.
generic

Exploiting Node.js deserialization bug for Remote Code Execution | OpSecX

https://opsecx.com/index.php/2017/02/08/exploiting-node-js-deserialization-bug-for-remote-code-execution/
generic
http://www.securityfocus.com/bid/96225

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmnode-serialize—ghsa

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
node-serialize———

Data Freshness Timeline

(refreshed 3× in last 7d / 26× 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.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-07 13:42 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-02 16:54 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-27 03:06 UTCEPSS rescore
  10. 2026-06-27 03:05 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-22 14:23 UTCEPSS rescore
  14. 2026-06-22 14:23 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-21 14:54 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-18 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-16 17:50 UTCEPSS rescore
  22. 2026-06-16 17:50 UTCEPSS rescore
  23. 2026-06-15 17:45 UTCEPSS rescore
  24. 2026-06-14 23:14 UTCEPSS rescore
  25. 2026-06-13 22:57 UTCEPSS rescore
Show 40 more
  1. 2026-06-12 23:09 UTCEPSS rescore
  2. 2026-06-10 22:15 UTCEPSS rescore
  3. 2026-06-10 13:19 UTCEPSS rescore
  4. 2026-06-07 15:22 UTCEPSS rescore
  5. 2026-06-07 15:22 UTCEPSS rescore
  6. 2026-06-06 13:45 UTCEPSS rescore
  7. 2026-06-06 13:45 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-05-31 00:14 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-29 13:41 UTCEPSS rescore
  14. 2026-05-22 21:15 UTCEPSS rescore
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-22 21:15 UTCEPSS rescore
  17. 2026-05-22 21:15 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-21 22:40 UTCEPSS rescore
  20. 2026-05-20 22:37 UTCEPSS rescore
  21. 2026-05-20 22:37 UTCEPSS rescore
  22. 2026-05-20 22:37 UTCEPSS rescore
  23. 2026-05-20 09:08 UTCEG score recompute
  24. 2026-05-20 09:08 UTCGHSA enrichment
  25. 2026-05-20 04:57 UTCEG score recompute
  26. 2026-05-20 04:57 UTCGHSA enrichment
  27. 2026-05-20 00:45 UTCEG score recompute
  28. 2026-05-20 00:45 UTCGHSA enrichment
  29. 2026-05-19 20:33 UTCEG score recompute
  30. 2026-05-19 20:33 UTCGHSA enrichment
  31. 2026-05-19 16:21 UTCEG score recompute
  32. 2026-05-19 16:21 UTCGHSA enrichment
  33. 2026-05-19 12:09 UTCEG score recompute
  34. 2026-05-19 12:09 UTCGHSA enrichment
  35. 2026-05-19 07:57 UTCEG score recompute
  36. 2026-05-19 07:57 UTCGHSA enrichment
  37. 2026-05-19 03:45 UTCEG score recompute
  38. 2026-05-19 03:45 UTCGHSA enrichment
  39. 2026-05-18 23:32 UTCEG score recompute
  40. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 GitHub PoC) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCuartu0/nodejshell
    First seen Aug 18, 2023

    Exploit de reverseshell para desserialização em NodeJs (CVE-2017-5941)

    Open source ↗
  • Exploit-DBEDB-50036
    First seen Jun 18, 2021

    Node.JS - 'node-serialize' Remote Code Execution (3)

    Open source ↗
  • Exploit-DBEDB-49552
    First seen Feb 10, 2021

    Node.JS - 'node-serialize' Remote Code Execution (2)

    Open source ↗
  • Exploit-DBEDB-45265
    First seen Feb 8, 2017

    Node.JS - 'node-serialize' Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2017-5941?
CVE-2017-5941 is a critical vulnerability published on February 9, 2017. An issue was discovered in the node-serialize package 0.0.4 for Node.js. Untrusted data passed into the unserialize() function can be exploited to achieve arbitrary code execution by passing a JavaScript Object with an Immediately Invoked Function Expression (IIFE).
When was CVE-2017-5941 disclosed?
CVE-2017-5941 was first published in the National Vulnerability Database on February 9, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5941 actively exploited?
CVE-2017-5941 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-5941?
CVE-2017-5941 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-5941?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5941, 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-2017-5941

Explore →

Is Your Infrastructure Affected by CVE-2017-5941?

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

Start Free Scan →Browse All CVEs