VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

node-node-forge: vulnerability history, versions and safety

node-node-forge is a package in the Debian ecosystem. Vulert records 11 vulnerabilities for it across 6 releases, from Sep 2020 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded U11
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 26 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-node-forge vulnerabilities

Vulert verdict on node-node-forge i

Updated on 23 Oct 2026

Careful: 3 of the 11 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 11 vulnerabilities on record across 5 years, 3 in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 5 years · 3 in the last year i
  • Latest disclosure 26 Nov 2025 i
  • Highest CVSS 8.6 i
  • With no published fix 3 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for node-node-forge, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.3.0~dfsg-1 U3 No Details →
1.2.1~dfsg-2 U3 No Details →
1.2.1~dfsg-1 U3 No Details →
0.10.0~dfsg-4 U3 No Details →
0.10.0~dfsg-3 U9 No Details →
0.10.0~dfsg-3+deb11u1 U3 No Details →

Newest 6 of 6 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2022 6
  • 2025 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for node-node-forge

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical ASN.1 Structure Vulnerability in Node-Forge Package 8.6 high No fix published 25 Nov 2025
Critical Vulnerability in node-forge: Lenient RSA PKCS#1 Signature Verification 7.5 high 0.10.0~dfsg-3+deb11u1 18 Mar 2022
Critical Vulnerability in node-forge: Insecure RSA PKCS#1 v1.5 Signature Verification 7.5 high 0.10.0~dfsg-3+deb11u1 18 Mar 2022
Prototype Pollution Vulnerability in node-forge Package 7.3 high 0.10.0~dfsg-1 01 Sep 2020
Insecure RSA PKCS#1 v1.5 Signature Verification in node-forge 5.3 medium 0.10.0~dfsg-3+deb11u1 18 Mar 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About node-node-forge

Is node-node-forge safe to use?

Vulert records 11 vulnerabilities for node-node-forge in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does node-node-forge have?

11 vulnerabilities are recorded for node-node-forge in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-node-forge vulnerabilities disclosed?

3 vulnerabilities were recorded for node-node-forge in the last 12 months, and the oldest entry in this database dates to 01 Sep 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of node-node-forge are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor node-node-forge for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-node-forge version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.