CVE-2017-5941

What it is

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).

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

61.0% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2017-02-09 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2017-02-09 19:59 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 01:21 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 61.0% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: none linked yet, which raises it.
• It meets the bar for Drop everything: critical, and exploited or very likely to be.

Details

Published

2017-02-09 19:59 UTC

Last modified

2026-06-17 01:21 UTC

Exploit probability

61.0% · EPSS, next 30 days

Weakness

CWE-502 · Unsafe deserialization

Record status

Modified

Affected

• node-serialize Project node-serialize ≤ 0.0.4

Attack profile CVSS 3.1 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-5941.md and follow it. Check whether this project is affected by CVE-2017-5941. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge