CVE-2025-71058

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-07. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Dual DHCP DNS Server 8.01 improperly accepts and caches UDP DNS responses without validating that the response originates from a legitimate configured upstream DNS server. The implementation matches responses primarily by TXID and inserts results into the cache, enabling a remote attacker to inject forged responses and poison the DNS cache, potentially redirecting victims to attacker-controlled destinations.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation none (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.

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

April 7, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No fix on record yet.
Web page

Dual DHCP DNS Server Windows/Linux download | SourceForge.net

https://sourceforge.net/projects/dhcp-dns-server/
Web page

Security-Advisory/CVE-2025-71058 at main · FPokerFace/Security-Advisory · GitHub

https://github.com/FPokerFace/Security-Advisory/tree/main/CVE-2025-71058
Web page

Security-Advisory/CVE-2025-71058/poc.c at main · FPokerFace/Security-Advisory · GitHub

https://github.com/FPokerFace/Security-Advisory/blob/main/CVE-2025-71058/poc.c

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 34× 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 99 of 272 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 173 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71058?
CVE-2025-71058 is a critical-severity vulnerability; its CVE record was published on April 7, 2026. Dual DHCP DNS Server 8.01 improperly accepts and caches UDP DNS responses without validating that the response originates from a legitimate configured upstream DNS server. The implementation matches responses primarily by TXID and inserts results into the cache, enabling a remote attacker to inject…
When was the CVE record for CVE-2025-71058 published?
The CVE record for CVE-2025-71058 was published on April 7, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2025-71058 actively exploited?
CVE-2025-71058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71058?
CVE-2025-71058 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-71058?
No fix for CVE-2025-71058 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-71058

Explore →

Is Your Infrastructure Affected by CVE-2025-71058?

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

Book a Demo →Browse All CVEs