npm package
node-forge 1.3.3 vulnerabilities, and what to upgrade to
node-forge 1.3.3 has 4 known vulnerabilities (4 rated high or critical); 1.4.0 fixes 3 of them, and 1 has no fixed version yet. 1.4.0 has 1 known vulnerability of its own, and so does every newer release we checked.
npm (opens in a new tab) describes it as “JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.”
- Known vulnerabilities
- 4
- 4 rated high or critical
- Released
- Dec 2, 2025
- Latest is 1.4.0
- Downloads last week
- 3M
- 8% of node-forge downloads
- Licence
- (BSD-3-Clause OR GPL-2.0)
- Dependencies
- None
- Resolved by deps.dev
What to upgrade to
Every newer release we checked still has known vulnerabilities. The fewer, the better.
Fixes 3 of the 4 known vulnerabilities and the newest 1.x release and the latest release. Released Mar 24, 2026.
1 known vulnerability, worst rated warning
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- CriticalVulnerability
4 known vulnerabilities in node-forge 1.3.3
EPSS: top 42%4 rated high or critical. Most serious: CVE-2026-33891, Forge has Denial of Service via Infinite Loop in BigInteger.modInverse() with Zero Input. Upgrading to 1.4.0 fixes 3 of them; 1 has no fixed version listed.
- LowOutdated
node-forge 1.3.3 is a minor version behind
Latest release is 1.4.0.
Every advisory for node-forge 1.3.3
Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.
CriticalCVE-2026-33891 on OSV.dev (opens in a new tab)GHSA-5m6q-g25r-mvwxEPSS: top 42%
Forge has Denial of Service via Infinite Loop in BigInteger.modInverse() with Zero Input
Fixed in 1.4.0. Published Mar 26, 2026.
CriticalCVE-2026-33896 on OSV.dev (opens in a new tab)GHSA-2328-f5f3-gj25EPSS: top 59%
Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)
Fixed in 1.4.0. Published Mar 26, 2026.
CriticalCVE-2026-33895 on OSV.dev (opens in a new tab)GHSA-q67f-28xg-22rwEPSS: top 61%
Forge has signature forgery in Ed25519 due to missing S > L check
Fixed in 1.4.0. Published Mar 26, 2026.
CriticalCVE-2026-33894 on OSV.dev (opens in a new tab)CVE-2026-85393EPSS: top 63%
node-forge RSA PKCS#1 v1.5 signature verification accepts extra nested DigestAlgorithm elements
No fixed version listed yet. Published Sep 3, 2026.
Who is still on a vulnerable node-forge
100% of last week’s 40M node-forge downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is node-forge the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly node-forge 1.3.3, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.
Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.