Chaindigitalbazaar · forgenpm:node-forge
digitalbazaar forge: incomplete fixes (2022–2026)
3 CVEs over 3 generations, 18 Mar 2022 to 3 Sep 2026.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2022-2477118 Mar 2022 First in the chain
- CVE-2026-3389427 Mar 2026 related to CVE-2022-24771
- CVE-2026-853933 Sep 2026 related to CVE-2022-24771incomplete fix for CVE-2026-33894
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2022-24771 | 18 Mar 2022 | Improper Verification of Cryptographic Signature in node-forge · fixed in 1.3.0 | First in chain | 16.4 |
| CVE-2026-33894 | 27 Mar 2026 | Forge has signature forgery in RSA-PKCS due to ASN.1 extra field | CVE-2022-24771 · related · High | 13.5 |
| CVE-2026-85393 | 3 Sep 2026 | node-forge through 1.4.0 RSA PKCS#1 v1.5 Signature Forgery via Nested DigestAlgorithm Padding | CVE-2022-24771 · related · High | 10.4 |