CVE-2026-54729
SSRF bug in DSSRF Node.js lib treats localhost as safe when DNS returns NXDOMAIN.
Is CVE-2026-54729 being exploited?
Not confirmed. CVE-2026-54729 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-54729?
CVE-2026-54729 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54729?
Yes. A fix has been recorded for CVE-2026-54729. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54729 affect?
CVE-2026-54729 affects DSSRF < 1.0.5, Node.js applications using DSSRF, Services relying on is_url_safe. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54729?
Upgrade DSSRF to >=1.0.5 and validate DNS fallback and egress controls
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Server-side request forgery: attackers can access localhost/internal services and abuse internal endpoints or exfiltrate data.
Patch when possible
- affected< 1.0.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.