CVE-2026-54729

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-51574 (ENISA EUVD) · GHSA-5846-7qm3-r52j (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 31, 2026

Last Modified

October 23, 2026

Advisory Details (3)

Auto-updated Jul 31, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit 668c21792cd1 (HackingRepo/dssrf-js)

Fix landed in HackingRepo/dssrf-js commit 668c21792cd1 — awaiting tagged release

https://github.com/HackingRepo/dssrf-js/commit/668c21792cd1252baf779a176aa652e2b4c0067d
GitHub pull request

Use dns.lookup and dns.resolve4 not just dns.resolve4 alone

Fix merged in HackingRepo/dssrf-js PR #102 on 2026-06-09 — awaiting tagged release

https://github.com/HackingRepo/dssrf-js/pull/102
GitHub advisoryMentions a patch (unverified)

any users using 1.1.1.1 DNS is impacted by SSRF · Advisory · HackingRepo/dssrf-js · GitHub

https://github.com/HackingRepo/dssrf-js/security/advisories/GHSA-5846-7qm3-r52j

Vendor Advisories for CVE-2026-54729(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmdssrf @ 1.0.5 (fixes <= 1.0.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
dssrf—
  • every version up to 1.0.5: fixed in 1.0.5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 154 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 54 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-5846-7qm3-r52j · GitHub severity HIGH
  3. 2026-11-01 07:44 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-27 21:02 UTCEG score recompute
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 14:19 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-23 23:28 UTCEG score recompute
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-18 03:30 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-17 03:53 UTCEG score recompute
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 75 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:39 UTCEG score recompute
  6. 2026-10-11 16:54 UTCEG score recompute
  7. 2026-10-11 14:17 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-06 23:50 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-05 19:55 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-04 23:50 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-04 06:29 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-10-02 16:49 UTCEG score recompute
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-01 02:46 UTCEG score recompute
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  26. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  27. 2026-09-29 06:49 UTCEG score recompute
  28. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  29. 2026-09-27 18:43 UTCEG score recompute
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  32. 2026-09-25 04:52 UTCEG score recompute
  33. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  34. 2026-09-23 23:54 UTCEG score recompute
  35. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  36. 2026-09-22 21:34 UTCEG score recompute
  37. 2026-09-22 07:37 UTCEG score recompute
  38. 2026-09-20 21:13 UTCEG score recompute
  39. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  40. 2026-09-19 23:42 UTCEG score recompute
  41. 2026-09-19 04:00 UTCEG score recompute
  42. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  43. 2026-09-18 01:16 UTCEG score recompute
  44. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  45. 2026-09-17 01:24 UTCEG score recompute
  46. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-09-16 05:28 UTCEG score recompute
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  49. 2026-09-15 07:06 UTCEG score recompute
  50. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-09-14 04:18 UTCEG score recompute
  52. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  53. 2026-09-13 02:25 UTCEG score recompute
  54. 2026-09-12 00:31 UTCEG score recompute
  55. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  56. 2026-09-10 18:55 UTCEG score recompute
  57. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  58. 2026-09-09 07:02 UTCEG score recompute
  59. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  60. 2026-09-07 19:30 UTCEG score recompute
  61. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  62. 2026-09-06 20:47 UTCEG score recompute
  63. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  64. 2026-09-05 18:51 UTCEG score recompute
  65. 2026-09-04 16:58 UTCEG score recompute
  66. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  67. 2026-09-03 09:07 UTCEG score recompute
  68. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  69. 2026-09-01 22:31 UTCEG score recompute
  70. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  71. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  72. 2026-08-31 00:12 UTCEG score recompute
  73. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  74. 2026-08-30 11:16 UTCEG score recompute
  75. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54729?
CVE-2026-54729 is a high-severity vulnerability; its CVE record was published on July 31, 2026. 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…
When was the CVE record for CVE-2026-54729 published?
The CVE record for CVE-2026-54729 was published on July 31, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-54729 actively exploited?
CVE-2026-54729 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54729?
CVE-2026-54729 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54729?
A fix for CVE-2026-54729 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54729 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54729

Explore →

Is Your Infrastructure Affected by CVE-2026-54729?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs