CVE-2026-54729 dssrf: any users using 1.1.1.1 DNS is impacted by SSRF
An SSRF vulnerability in the dssrf library allows bypassing localhost protections when using Cloudflare DNS, potentially exposing internal services.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54729?
CVE-2026-54729 is a high-severity server-side request forgery vulnerability in HackingRepo dssrf-js, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
DSSRF is a Node.js library that provides a wide range of utilities and advanced SSRF defense checks. Prior to 1.0.5, 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. This issue is fixed in version 1.0.5.
Weakness: CWE-918
Which versions are affected by CVE-2026-54729?
2 open source packages ship an affected version, including dssrf.
| Package | Affected | Fixed in |
|---|---|---|
dssrf npm | All versions | 1.0.5 |
dssrf npm | All versions | 1.0.5 |
How do I fix CVE-2026-54729?
Upgrade dssrf to 1.0.5 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-54729 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54729 exists.
Sources
Also known as GHSA-5846-7qm3-r52j.