HighGHSA-86w9-cpqp-85rvCVE-2026-33894CVE-2026-85393GHSA-ppp5-5v6c-4jwp
node-forge RSA PKCS#1 v1.5 signature verification accepts extra nested DigestAlgorithm elements
Published 3 Sept 2026 · Updated 1 Oct 2026
Affected package
node-forgenpm
- Affected
- <=1.4.0
- Fixed in
- No fix released
Details
node-forge through 1.4.0 fails to validate element count in nested DigestAlgorithm sequences during RSA PKCS#1 v1.5 signature verification. Attackers can embed garbage bytes inside the DigestAlgorithm sequence to forge valid signatures for arbitrary messages using low-exponent RSA keys. This is an incomplete fix for CVE-2026-33894.
Is GHSA-86w9-cpqp-85rv in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected node-forge, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-85393
- Linkgithub.com/digitalbazaar/forge/issues/1149
- Linkgithub.com/digitalbazaar/forge/pull/1152
- Advisorygithub.com/advisories/GHSA-ppp5-5v6c-4jwp
- Packagegithub.com/digitalbazaar/forge
- Linkgithub.com/digitalbazaar/forge/blob/v1.4.0/lib/asn1.js
- Linkgithub.com/digitalbazaar/forge/blob/v1.4.0/lib/rsa.js
- Linkwww.vulncheck.com/advisories/node-forge-through-1.4.0-rsa-pkcs-1-1.5-signature-forgery-via-nested-digestalgorithm-padding
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.