PatchTheCVEforge vulnerabilities and fixes
Recent CVEs affecting forge, with upgrade or downgrade steps. 4 tracked.
forge has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-03-27. Highest priority: CVE-2026-33891 (score 48/100).
- CVE-2026-33891 HIGH 7.5 UPGRADE Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
- CVE-2026-33895 HIGH 7.5 UPGRADE Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
- CVE-2026-33896 HIGH 7.4 UPGRADE Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
- CVE-2026-33894 HIGH 7.5 UPGRADE Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
FAQ
How do I fix forge vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is forge being exploited right now?
None of the tracked forge CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which forge CVE should I patch first?
CVE-2026-33891 currently ranks highest (48/100): Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript.