Prototype Pollution in node-forge debug API.
Impact
The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.
Patches
The forge.debug API and related functions were removed in 1.0.0.
Workarounds
Don't use the forge.debug API directly or indirectly with untrusted input.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in forge.
- Email us at support@digitalbazaar.com.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | node-forge | < 1.0.0 | 1.0.0 |
References
- Weakness (CWE)
CWE-1321- Platform
- npm
- Package
node-forge- Disclosed
- 08.01.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-5rrq-pxf6-6jx5 - CC BY 4.0
Vulnerability history: node-forge
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 15
- First → latest
- 09.2020 03.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 9
- Medium 3
- Low 3
Disclosures per year
- 2020: 1
- 2021: 0
- 2022: 7
- 2023: 0
- 2024: 0
- 2025: 3
- 2026: 4
-
Prototype Pollution in node-forge debug API. this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.