CVE-2017-5941
CVE-2017-5941 is a critical-severity vulnerability in Node-serialize Project Node-serialize with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 61% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-502.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- CVSS v2: 7.5
- EPSS exploit prediction: 61% (99th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-502
- Affected product: Node-serialize Project Node-serialize
- Published:
- Last modified:
Description
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).
Frequently asked questions
- What is CVE-2017-5941?
- 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).
- How severe is CVE-2017-5941?
- CVE-2017-5941 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2017-5941 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 61% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2017-5941?
- CVE-2017-5941 affects Node-serialize Project Node-serialize. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2017-5941?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2017-5941 published?
- CVE-2017-5941 was published on 2017-02-09 and last updated on 2026-06-17.
References
- http://packetstormsecurity.com/files/161356/Node.JS-Remote-Code-Execution.html
- http://packetstormsecurity.com/files/163222/Node.JS-Remote-Code-Execution.html
- http://www.securityfocus.com/bid/96225
- https://nodesecurity.io/advisories/311
- https://opsecx.com/index.php/2017/02/08/exploiting-node-js-deserialization-bug-for-remote-code-execution/
Affected products (1)
- cpe:2.3:a:node-serialize_project:node-serialize:*:*:*:*:*:node.js:*:*
Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities
- CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
- CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
- CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.
- CVE-2026-20131 — Critical (CVSS 10.0): A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could…
- CVE-2026-25632 — Critical (CVSS 10.0): EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water…
- CVE-2025-14931 — Critical (CVSS 10.0): Hugging Face smolagents Remote Python Executor Deserialization of Untrusted Data Remote Code Execution Vulnerability.…
Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →