URL parsing in node-forge could lead to undesired behavior.
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-601.
Summary
### 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 - https://www.huntr.dev/bounties/41852c50-3c6d-4703-8c55-4db27164a4ae/ ### For more information If you have any questions or comments about this advisory: * Open an issue in [forge](https://github.com/digitalbazaar/forge) * Email us at [email protected]
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | node-forge (npm) | before 1.0.0 | 1.0.0 | Patch available | GHSA-gf8q-jrpm-jvxq |
- node-forge (npm) Vendor— Affected before 1.0.0 Fixed in 1.0.0 Patch available GHSA-gf8q-jrpm-jvxq
Remediation
- Fix · GHSA-gf8q-jrpm-jvxq node-forge (npm) Fixed in 1.0.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-gf8q-jrpm-jvxq
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences