dssrf has an SSRF bypass with remove_at_symbol_in_string

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-54722: 0.57% estimated exploitation activity in the next 30 days; percentile 47.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary isurlsafe in v1.0.3 contains an SSRF bypass. removeatsymbolinstring is applied to the raw URL string before new URL() parses it. This strips the @ that separates userinfo from host, corrupting the hostname so internal IPs are never checked. Vulnerability In helpers.ts, isurlsafe does: What happens step by step Input: http://evil.com@127.0.0.1/ 1. removeatsymbolinstring → http://evil.com127.0.0.1/ 2. new URL(...) → hostname = "evil.com127.0.0.1" 3. Not a bare IP, not IPv6 → passes all IP checks 4. ishostnameresolvetointernalip("evil.com127.0.0.1") → NXDOMAIN → returns false 5. Result: true (safe) — but any HTTP client using the original URL connects to 127.0.0.1 Proof of Concept Root Cause @ in a URL separates userinfo (credentials) from host. Stripping it from the raw string before parsing destroys that boundary. The fix is to reject any URL that contains a userinfo component after parsing. Suggested Fix Remove the removeatsymbolinstring call from isurlsafe and add a userinfo…

Published by the source

30 Jul 2026, 16:26 UTC

Last modified by the source

30 Jul 2026, 21:23 UTC

Source last checked

26 Oct 2026, 13:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cg4g-m8jx-vjv2

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

# Patch Next advisory brief: CVE-2026-54722

Advisory: dssrf has an SSRF bypass with remove_at_symbol_in_string
IDs: CVE-2026-54722, GHSA-cg4g-m8jx-vjv2
Record: https://patchnext.com/advisories/cve-2026-54722 (revision 1, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dssrf 1.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm dssrf: affected <= 1.0.3; fixed in 1.0.4

## Suggested inspection (read-only)
- `npm ls dssrf --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 dssrf.
- 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://github.com/advisories/GHSA-cg4g-m8jx-vjv2 (GitHub-reviewed advisory GHSA-cg4g-m8jx-vjv2 lists affected ranges: npm dssrf >=0 <=1.0.3)

Commands are suggestions: review each one before running it.