CVE-2026-44232: dssrf Every IPv6 Category Bypasses Is_url_safe Vulnerability

Q: What is CVE-2026-44232?

CVE-2026-44232 is a security vulnerability in dssrf involving every IPv6 category bypasses is_url_safe under CWE-791: Incomplete Filtering of Special Elements.

Q: Which dssrf versions are affected?

Affected versions include releases prior to 1.0.3 across affected packages: dssrf.

Q: What version fixes CVE-2026-44232?

Upgrading to 1.0.3 (or the latest patched release for your respective branch) resolves the vulnerability.

Q: Is dssrf affected?

Yes, dssrf is affected in releases prior to 1.0.3. Upgrade your dependency to 1.0.3 or later.

Q: What CWE is associated with CVE-2026-44232?

CVE-2026-44232 is classified under CWE-791: Incomplete Filtering of Special Elements (The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.).

Q: How can I check npm dependencies for CVE-2026-44232?

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.

HIGH

Advisory Identifier: GHSA-8p33-q827-ghj5

CWE-791

Published 2026-05-06

Advisory Summary

CVE-2026-44232 is a HIGH every ipv6 category bypasses is_url_safe vulnerability (CWE-791: Incomplete Filtering of Special Elements) affecting dssrf libraries in the npm ecosystem. The issue involves every ipv6 category bypasses is_url_safe. Remediation is available by upgrading affected packages to version 1.0.3.

CVE-2026-44232 at a Glance

CVE Identifier CVE-2026-44232

GHSA Identifier GHSA-8p33-q827-ghj5

Severity HIGH

CVSS v3.1 Base Score N/A

CWE Classification CWE-791: Incomplete Filtering of Special Elements

Affected Product dssrf

Package Ecosystem npm

Published Date 2026-05-06

Last Updated 2026-06-18

How to Fix CVE-2026-44232

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.3

npm install dssrf@1.0.3

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-44232, 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.3), 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-791: Incomplete Filtering of Special Elements, where the product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component. 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

A vulnerability on dssrf allow, an attacker to use, one of them following ipv6 ```rust Input Category http://[::1]/ IPv6 loopback http://[fc00::1]/ IPv6 ULA http://[fe80::1]/ IPv6 link-local http://[::ffff:127.0.0.1]/ IPv4-mapped loopback http://[::ffff:169.254.169.254]/ IPv4-mapped IMDS http://[::ffff:100.64.0.1]/ IPv4-mapped CGNAT http://[64:ff9b::7f00:1]/ NAT64 well-known prefix http://[64:ff9b:1::1]/ NAT64 local-use (RFC 8215) http://[5f00::1]/ SRv6 SID (RFC 9602) http://[3fff::1]/ IPv6 documentation (RFC 9637) http://[fec0::1]/ IPv6 site-local (deprecated, RFC 3879) http://[::127.0.0.1]/ IPv4-compatible IPv6 ``` one of those to bypass dssrf and the attacker get **SSRF**, we claim that ipv6 disabled entirely that is wrong on our documentation ### POC ```bash mkdir dssrf-poc && cd dssrf-poc npm init -y >/dev/null npm install dssrf@^1.0.2 cat > audit.js <<'EOF' const dssrf = require('dssrf'); const cases = [ ['http://[::1]/', 'IPv6 loopback'], ['http://[fc00::1]/', 'IPv6 ULA'], ['http://[fe80::1]/', 'IPv6 link-local'], ['http://[::ffff:127.0.0.1]/', 'IPv4-mapped loopback'], ['http://[::ffff:169.254.169.254]/', 'IPv4-mapped IMDS'], ['http://[64:ff9b::7f00:1]/', 'NAT64 well-known + 127.0.0.1'], ['http://[64:ff9b:1::1]/', 'NAT64 local-use (RFC 8215)'], ['http://[5f00::1]/', 'SRv6 SID (RFC 9602)'], ['http://[fec0::1]/', 'IPv6 site-local deprecated'], ['http://127.0.0.1/', 'IPv4 loopback (control)'], ['http://10.0.0.1/', 'IPv4 RFC1918 (control)'], ['http://8.8.8.8/', 'PUBLIC IPv4 (control)'], ]; (async () => { for (const [url, label] of cases) { const safe = await dssrf.is_url_safe(url); console.log(`${safe ? '✓ALLOW' : '·block'} ${url.padEnd(40)} ${label}`); } })(); EOF node audit.js ``` ### Credit Million Thank's to <brmenna@gmail.com> for reporting that responsibly. ### Update Users need to update from now to dssrf 1.0.3 ### Lessons Learned AS we see in the past and today, a lot of advisories or cves bypasses uses IPv6, and IPv6 is the weakest link to be configured correctly and rarely properly tested, Since we blocked ipv4, our ipv6 blocking logic completly broken and never works

CVE-2026-44232 Affected dssrf Versions

1 component(s)

Fixed Versions:

1.0.3

Product / Package	Ecosystem	Affected Versions	Fixed Version
dssrf npm/dssrf	npm	< 1.0.3	1.0.3

References

GitHub Advisory / Wiki ADVISORY

https://github.com/HackingRepo/dssrf-js/security/advisories/GHSA-8p33-q827-ghj5

NVD — CVE-2026-44232 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-44232

dssrf Source Repository REPOSITORY

https://github.com/HackingRepo/dssrf-js

Frequently Asked Questions

What is CVE-2026-44232?

CVE-2026-44232 is a security vulnerability in dssrf involving every IPv6 category bypasses is_url_safe under CWE-791: Incomplete Filtering of Special Elements.

Which dssrf versions are affected?

Affected versions include releases prior to 1.0.3 across affected packages: dssrf.

What version fixes CVE-2026-44232?

Upgrading to 1.0.3 (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.3. Upgrade your dependency to 1.0.3 or later.

What CWE is associated with CVE-2026-44232?

CVE-2026-44232 is classified under CWE-791: Incomplete Filtering of Special Elements (The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.).

How can I check npm dependencies for CVE-2026-44232?

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-8p33-q827-ghj5",
  "modified" : "2026-06-18T22:54:14Z",
  "published" : "2026-05-06T18:13:32Z",
  "aliases" : [ "CVE-2026-44232" ],
  "summary" : "dssrf: every IPv6 category bypasses is_url_safe",
  "details" : "A vulnerability on dssrf allow, an attacker to use, one of them following ipv6\n\n```rust\nInput\tCategory\nhttp://[::1]/\tIPv6 loopback\nhttp://[fc00::1]/\tIPv6 ULA\nhttp://[fe80::1]/\tIPv6 link-local\nhttp://[::ffff:127.0.0.1]/\tIPv4-mapped loopback\nhttp://[::ffff:169.254.169.254]/\tIPv4-mapped IMDS\nhttp://[::ffff:100.64.0.1]/\tIPv4-mapped CGNAT\nhttp://[64:ff9b::7f00:1]/\tNAT64 well-known prefix\nhttp://[64:ff9b:1::1]/\tNAT64 local-use (RFC 8215)\nhttp://[5f00::1]/\tSRv6 SID (RFC 9602)\nhttp://[3fff::1]/\tIPv6 documentation (RFC 9637)\nhttp://[fec0::1]/\tIPv6 site-local (deprecated, RFC 3879)\nhttp://[::127.0.0.1]/\tIPv4-compatible IPv6\n```\n\none of those to bypass dssrf and the attacker get **SSRF**, we claim that ipv6 disabled entirely that is wrong on our documentation\n\n### POC\n\n```bash\nmkdir dssrf-poc && cd dssrf-poc\nnpm init -y >/dev/null\nnpm install dssrf@^1.0.2\ncat > audit.js <<'EOF'\nconst dssrf = require('dssrf');\nconst cases = [\n  ['http://[::1]/',                         'IPv6 loopback'],\n  ['http://[fc00::1]/',                     'IPv6 ULA'],\n  ['http://[fe80::1]/',                     'IPv6 link-local'],\n  ['http://[::ffff:127.0.0.1]/',            'IPv4-mapped loopback'],\n  ['http://[::ffff:169.254.169.254]/',      'IPv4-mapped IMDS'],\n  ['http://[64:ff9b::7f00:1]/',             'NAT64 well-known + 127.0.0.1'],\n  ['http://[64:ff9b:1::1]/',                'NAT64 local-use (RFC 8215)'],\n  ['http://[5f00::1]/',                     'SRv6 SID (RFC 9602)'],\n  ['http://[fec0::1]/',                     'IPv6 site-local deprecated'],\n  ['http://127.0.0.1/',                     'IPv4 loopback (control)'],\n  ['http://10.0.0.1/',                      'IPv4 RFC1918 (control)'],\n  ['http://8.8.8.8/',                       'PUBLIC IPv4 (control)'],\n];\n(async () => {\n  for (const [url, label] of cases) {\n    const safe = await dssrf.is_url_safe(url);\n    console.log(`${safe ? '✓ALLOW' : '·block'}  ${url.padEnd(40)}  ${label}`);\n  }\n})();\nEOF\nnode audit.js\n```\n\n### Credit\nMillion Thank's to <brmenna@gmail.com> for reporting that responsibly.\n\n### Update\nUsers need to update from now to dssrf 1.0.3\n\n### Lessons Learned\nAS we see in the past and today, a lot of advisories or cves bypasses uses IPv6, and IPv6 is the weakest link to be configured correctly and rarely properly tested, Since we blocked ipv4, our ipv6 blocking logic completly broken and never works",
  "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.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/HackingRepo/dssrf-js/security/advisories/GHSA-8p33-q827-ghj5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44232"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/HackingRepo/dssrf-js"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-791" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-06T18:13:32Z",
    "nvd_published_at" : "2026-05-12T21:16:16Z"
  }
}

CVSS V4

N/A HIGH

Attack Vector N/A

Attack Complexity N/A

Privileges Required N/A

User Interaction N/A

Scope N/A

Confidentiality N/A

Integrity N/A

Availability N/A

Vector String

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

Advisory Metadata

Source ID: GHSA-8p33-q827-ghj5
Schema Version: 1.4.0
Published: 2026-05-06 18:13
Last Modified: 2026-06-18 22:54
Database Record File: advisories/github-reviewed/2026/05/GHSA-8p33-q827-ghj5/GHSA-8p33-q827-ghj5.json