npm package report

Is node-forge safe?

15 known vulnerabilities, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
4.6

CyberXYZ composite, out of 10

fig. 01 — GHSA-ppp5-5v6c-4jwp, the advisory selected below

// advisories

GHSA-ppp5-5v6c-4jwp

HIGHCVE-2026-33894

RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling [Bleichenbacher style forgery](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/). This issue is similar to [CVE-2022-

Affected
< 1.4.0
Fixed in
1.4.0
Weakness
CWE-20
Published
2026-03-26
Source
github

GHSANVDMITREreferencereferencereferencereferencereference

// 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:30 UTC. The most recent advisory here was published 2026-03-26. Updated continuously from NVD, GHSA, OSV and CNA feeds.

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