npm package report

Is socket.io-parser safe?

5 known vulnerabilities, worst severity CRITICAL.

cvss
10.0

how bad it is if exploited, out of 10

epss
1.2%

chance of exploitation in the next 30 days

xyz score
5.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-qm95-pgcg-qqfq, the advisory selected below

// advisories

GHSA-qm95-pgcg-qqfq

CRITICALCVE-2022-2421

Due to improper type validation in the socket.io-parser library (which is used by the socket.io and socket.io-client packages to encode and decode Socket.IO packets), it is possible to overwrite the placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object.

Affected
>= 4.0.0, < 4.0.5, < 3.3.3, >= 4.1.0, < 4.2.1, >= 3.4.0, < 3.4.2
Fixed in
4.0.5
Weakness
CWE-20
Published
2022-10-26
Source
github

GHSANVDMITREreferencereferencereferencereferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 01:37 UTC. The most recent advisory here was published 2026-08-03. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is socket.io-parser safe? npm package security report | CyberXYZ