Vulnerabilities in pkg:npm/dssrf

PACKAGE
Advisory Identifier: GHSA-5846-7qm3-r52j
Share
Advisory Summary

CVE-2026-54729 is a HIGH any users using 1.1.1.1 dns vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting dssrf libraries in the npm ecosystem. The issue involves any users using 1.1.1.1 dns is impacted by ssrf. Remediation is available by upgrading affected packages to version 1.0.5.

3 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/dssrf

3 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/dssrf. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-5846-7qm3-r52j CVE-2026-54729 HIGH dssrf: any users using 1.1.1.1 DNS is impacted by SSRF
GHSA-cg4g-m8jx-vjv2 CVE-2026-54722 HIGH dssrf has an SSRF bypass with remove_at_symbol_in_string
GHSA-8p33-q827-ghj5 CVE-2026-44232 HIGH dssrf: every IPv6 category bypasses is_url_safe

CVE-2026-54729 at a Glance

CVE Identifier CVE-2026-54729
GHSA Identifier GHSA-5846-7qm3-r52j
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product dssrf
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-54729

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.5 
npm install dssrf@1.0.5
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-54729, 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.5), 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-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. 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 can treat localhost as safe when DNS resolver 1.1.1.1 returns NXDOMAIN because dns.resolve4 yields no address and no dns.lookup fallback occurs, allowing server-side request forgery. ## POC Example to simulate 1.1.1.1 in version before 1.5.0 of dssrf: ```js import { is_url_safe } from '../dist/helpers.js'; import dns from 'dns'; dns.setServers(['1.1.1.1']); const TARGET = 'http://localhost/admin'; console.log(`Testing: ${TARGET}`); console.log(`Current DNS Servers: ${dns.getServers()}`); const result = await is_url_safe(TARGET); if (result === true) { console.log('dssrf treated localhost as SAFE because 1.1.1.1 returned NXDOMAIN.'); } else { console.log('dssrf blocked localhost.'); } ```

CVE-2026-54729 Affected dssrf Versions

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

References

GitHub Advisory / Wiki ADVISORY
https://github.com/HackingRepo/dssrf-js/security/advisories/GHSA-5846-7qm3-r52j
dssrf Source Repository REPOSITORY
https://github.com/HackingRepo/dssrf-js/pull/102
Security Fix Commit FIX COMMIT
https://github.com/HackingRepo/dssrf-js/commit/668c21792cd1252baf779a176aa652e2b4c0067d
dssrf Source Repository REPOSITORY
https://github.com/HackingRepo/dssrf-js

Frequently Asked Questions

What is CVE-2026-54729?
CVE-2026-54729 is a security vulnerability in dssrf involving any users using 1.1.1.1 DNS is impacted by SSRF under CWE-918: Server-Side Request Forgery (SSRF).
Which dssrf versions are affected?
Affected versions include releases prior to 1.0.5 across affected packages: dssrf.
What version fixes CVE-2026-54729?
Upgrading to 1.0.5 (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.5. Upgrade your dependency to 1.0.5 or later.
What CWE is associated with CVE-2026-54729?
CVE-2026-54729 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2026-54729?
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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5846-7qm3-r52j",
  "modified" : "2026-07-31T16:58:42Z",
  "published" : "2026-07-31T16:58:42Z",
  "aliases" : [ "CVE-2026-54729" ],
  "summary" : "dssrf: any users using 1.1.1.1 DNS is impacted by SSRF",
  "details" : "## Summary\n\nis_url_safe can treat localhost as safe when DNS resolver 1.1.1.1 returns NXDOMAIN because dns.resolve4 yields no address and no dns.lookup fallback occurs, allowing server-side request forgery.\n\n## POC\n\nExample to simulate 1.1.1.1 in version before 1.5.0 of dssrf:\n\n```js\nimport { is_url_safe } from '../dist/helpers.js';\nimport dns from 'dns';\n\n\ndns.setServers(['1.1.1.1']);\n\nconst TARGET = 'http://localhost/admin';\n\nconsole.log(`Testing: ${TARGET}`);\nconsole.log(`Current DNS Servers: ${dns.getServers()}`);\n\nconst result = await is_url_safe(TARGET);\n\nif (result === true) {\n    console.log('dssrf treated localhost as SAFE because 1.1.1.1 returned NXDOMAIN.');\n} else {\n    console.log('dssrf blocked localhost.');\n}\n```",
  "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.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/security/advisories/GHSA-5846-7qm3-r52j"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/pull/102"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/commit/668c21792cd1252baf779a176aa652e2b4c0067d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/HackingRepo/dssrf-js"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-31T16:58:42Z",
    "nvd_published_at" : null
  }
}