CVE-2025-66678

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

An issue in the HwRwDrv.sys component of Nil Hardware Editor Hardware Read & Write Utility v1.25.11.26 and earlier allows attackers to execute arbitrary read and write operations via a crafted request.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
No patch confirmed yet.
generic

GitHub - cwjchoi01/CVE-2025-66678: CVE-2025-66678 · GitHub

https://github.com/cwjchoi01/CVE-2025-66678
generic

GitHub - Faintsnow/HE: HE - Hardware Read & Write utility is a powerful utility for hardware engineers, BIOS engineers, driver developers, QA engineers, performance test engineers, diagnostic engineers… etc. · GitHub

https://github.com/Faintsnow/HE

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:30 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-15 03:10 UTCEPSS rescore
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:36 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-08-30 19:16 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-28 21:40 UTCEPSS rescore
  19. 2026-08-27 14:24 UTCEPSS rescore
  20. 2026-08-26 14:45 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-24 14:16 UTCEPSS rescore
  23. 2026-08-23 00:18 UTCEPSS rescore
  24. 2026-08-21 23:48 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 63 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:47 UTCEPSS rescore
  3. 2026-08-17 13:46 UTCEPSS rescore
  4. 2026-08-16 14:55 UTCEPSS rescore
  5. 2026-08-16 02:13 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-15 01:29 UTCEPSS rescore
  8. 2026-08-15 01:18 UTCGHSA enrichment
  9. 2026-08-14 20:57 UTCGHSA enrichment
  10. 2026-08-14 13:00 UTCGHSA enrichment
  11. 2026-08-14 08:36 UTCEG score recompute
  12. 2026-08-14 08:36 UTCGHSA enrichment
  13. 2026-08-13 21:59 UTCEPSS rescore
  14. 2026-08-13 04:44 UTCGHSA enrichment
  15. 2026-08-13 00:21 UTCEG score recompute
  16. 2026-08-13 00:21 UTCGHSA enrichment
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-11 23:17 UTCEG score recompute
  19. 2026-08-11 23:17 UTCGHSA enrichment
  20. 2026-08-11 13:42 UTCEPSS rescore
  21. 2026-08-11 05:49 UTCEG score recompute
  22. 2026-08-11 05:49 UTCGHSA enrichment
  23. 2026-08-10 23:59 UTCEPSS rescore
  24. 2026-08-10 13:04 UTCGHSA enrichment
  25. 2026-08-10 07:56 UTCGHSA enrichment
  26. 2026-08-10 02:50 UTCGHSA enrichment
  27. 2026-08-09 22:21 UTCGHSA enrichment
  28. 2026-08-09 18:00 UTCEG score recompute
  29. 2026-08-09 18:00 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 13:38 UTCGHSA enrichment
  33. 2026-08-09 08:14 UTCEG score recompute
  34. 2026-08-09 08:14 UTCGHSA enrichment
  35. 2026-08-08 16:36 UTCEPSS rescore
  36. 2026-08-08 09:11 UTCGHSA enrichment
  37. 2026-08-08 04:49 UTCGHSA enrichment
  38. 2026-08-08 00:28 UTCGHSA enrichment
  39. 2026-08-07 20:06 UTCEG score recompute
  40. 2026-08-07 20:06 UTCGHSA enrichment
  41. 2026-08-07 16:26 UTCEPSS rescore
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-06 07:03 UTCGHSA enrichment
  44. 2026-08-06 02:42 UTCEG score recompute
  45. 2026-08-06 02:42 UTCGHSA enrichment
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:09 UTCEPSS rescore
  49. 2026-08-04 10:37 UTCEPSS rescore
  50. 2026-08-04 02:42 UTCEG score recompute
  51. 2026-08-04 02:42 UTCGHSA enrichment
  52. 2026-08-03 10:35 UTCEPSS rescore
  53. 2026-08-02 23:22 UTCGHSA enrichment
  54. 2026-08-02 19:00 UTCEG score recompute
  55. 2026-08-02 19:00 UTCGHSA enrichment
  56. 2026-08-02 02:26 UTCEPSS rescore
  57. 2026-08-01 04:15 UTCEPSS rescore
  58. 2026-07-30 16:27 UTCEPSS rescore
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-28 15:35 UTCEPSS rescore
  61. 2026-07-27 14:12 UTCEPSS rescore
  62. 2026-07-27 13:53 UTCEG score recompute
  63. 2026-07-27 13:53 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCcwjchoi01/CVE-2025-66678
    First seen Mar 1, 2026

    CVE-2025-66678

    Open source ↗

Frequently asked(5)

What is CVE-2025-66678?
CVE-2025-66678 is a critical vulnerability published on March 4, 2026. An issue in the HwRwDrv.sys component of Nil Hardware Editor Hardware Read & Write Utility v1.25.11.26 and earlier allows attackers to execute arbitrary read and write operations via a crafted request.
When was CVE-2025-66678 disclosed?
CVE-2025-66678 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-66678 actively exploited?
CVE-2025-66678 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all scored CVEs.
What is the CVSS score of CVE-2025-66678?
CVE-2025-66678 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-66678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-66678, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-66678?

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

Start Free Scan →Browse All CVEs