URL parsing in node-forge could lead to undesired behavior.
Impact
The regex used for the forge.util.parseUrl API would not properly parse certain inputs resulting in a parsed data structure that could lead to undesired behavior.
Patches
forge.util.parseUrl and other very old related URL APIs were removed in 1.0.0 in favor of letting applications use the more modern WHATWG URL Standard API.
Workarounds
Ensure code does not directly or indirectly call forge.util.parseUrl 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-601- Platform
- npm
- Package
node-forge- Disclosed
- 08.01.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-gf8q-jrpm-jvxq - 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
-
URL parsing in node-forge could lead to undesired behavior. 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.