Is socket.io-parser 4.2 vulnerable?
npm · 8 releases from 4.2.0 to 4.2.7 · latest socket.io-parser is 4.2.7 · checked 2 Nov 2026
No known advisories in the last release
socket.io-parser 4.2.7, the last 4.2 release, has no known advisories. 4 advisories affect earlier 4.2.x releases, so update to 4.2.7.
npm install socket.io-parser@4.2.7Fixed within 4.2.x, affecting earlier releases
Socket.IO: Zero-attachment Memory Exhaustion
- Affected
- >=4.0.0 <4.2.7 · >=3.4.0 <3.4.5 · <3.3.6
- Fixed in
- 3.3.6, 3.4.5, 4.2.7
socket.io allows an unbounded number of binary attachments
- Affected
- <3.3.5 · >=3.4.0 <3.4.4 · >=4.0.0 <4.2.6
- Fixed in
- 3.3.5, 3.4.4, 4.2.6
Insufficient validation when decoding a Socket.IO packet
- Affected
- >=4.0.4 <4.2.3 · >=3.4.0 <3.4.3 · <3.3.4
- Fixed in
- 3.3.4, 3.4.3, 4.2.3
Insufficient validation when decoding a Socket.IO packet
- Affected
- >=4.0.0 <4.0.5 · >=4.1.0 <4.2.1 · <3.3.3 · >=3.4.0 <3.4.2
- Fixed in
- 3.3.3, 3.4.2, 4.0.5, 4.2.1
Which of your client projects are still on socket.io-parser 4.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact socket.io-parser version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other socket.io-parser versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.