Answer in brief
CVE-2026-54729 records a High severity ssrf vulnerability in dssrf: any users using 1.1.1.1 DNS is impacted by SSRF. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-54729 records a High severity ssrf vulnerability in dssrf: any users using 1.1.1.1 DNS is impacted by SSRF. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update dssrf to 1.0.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSSRF describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54729 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| dssrfnpm | <=1.0.4 | 1.0.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54729 records a High severity ssrf vulnerability in dssrf: any users using 1.1.1.1 DNS is impacted by SSRF. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for dssrf.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate dssrf to 1.0.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSSRF describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54729 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| dssrfnpm | <=1.0.4 | 1.0.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54729 records a High severity ssrf vulnerability in dssrf: any users using 1.1.1.1 DNS is impacted by SSRF. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for dssrf.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard## 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.'); } ```
## 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.'); } ```