Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

URL parsing in node-forge could lead to undesired behavior.

GHSA-gf8q-jrpm-jvxq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (node-forge 1.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 Email us at support@digitalbazaar.com

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-gf8q-jrpm-jvxq

  2. Revision 1 · created ·

    Published from osv record GHSA-gf8q-jrpm-jvxq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-gf8q-jrpm-jvxq

Advisory: URL parsing in node-forge could lead to undesired behavior.
IDs: GHSA-gf8q-jrpm-jvxq
Record: https://patchnext.com/advisories/ghsa-gf8q-jrpm-jvxq (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node-forge 1.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-forge: affected < 1.0.0; fixed in 1.0.0

## Suggested inspection (read-only)
- `npm ls node-forge --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-forge.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gf8q-jrpm-jvxq (OSV record GHSA-gf8q-jrpm-jvxq lists affected ranges: npm node-forge >=0 <1.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-gf8q-jrpm-jvxq (GitHub-reviewed advisory GHSA-gf8q-jrpm-jvxq lists affected ranges: npm node-forge >=0 <1.0.0)

Commands are suggestions: review each one before running it.

Loading voting…