CVE-2025-71317

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-05. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.8EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

NetMan 204 contains a hard-coded backdoor account with the username and password 'eurek' that grants administrative access. A remote, unauthenticated attacker can authenticate through the cgi-bin/login.cgi endpoint (for example /cgi-bin/login.cgi?username=eurek&password=eurek, which due to lax parameter validation can be shortened to /cgi-bin/login.cgi?username=eurek%20eurek) to obtain administrator privileges, allowing them to alter device configuration, enable the telnet/SSH services, and reset local user credentials.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 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 total (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

June 5, 2026

Last Modified

October 7, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
No fix on record yet.
Web page

NetMan 204 Hard-coded Backdoor Credentials | Advisories | VulnCheck

https://www.vulncheck.com/advisories/netman-204-hard-coded-backdoor-credentials
Web page

NetMan 204

https://www.riello-ups.com/downloads/25-netman-204
Web page

Netman 204 - Remote command without authentication - Multiple hardware Exploit

https://www.exploit-db.com/exploits/52183

Vendor Advisories for CVE-2025-71317(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 36× 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 444 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 345 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71317?
CVE-2025-71317 is a critical-severity vulnerability; its CVE record was published on June 5, 2026. NetMan 204 contains a hard-coded backdoor account with the username and password 'eurek' that grants administrative access. A remote, unauthenticated attacker can authenticate through the cgi-bin/login.cgi endpoint (for example /cgi-bin/login.cgi?username=eurek&password=eurek, which due to lax…
When was CVE-2025-71317 made public?
CVE-2025-71317 was made public on February 4, 2025: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 5, 2026. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2025-71317 actively exploited?
CVE-2025-71317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71317?
CVE-2025-71317 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-71317?
No fix for CVE-2025-71317 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-71317 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-71317?

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

Book a Demo →Browse All CVEs