CVE-2025-9497

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 published 2026-03-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2025-209112 (ENISA EUVD) · GHSA-gv5m-4fg8-r764 (GitHub Security Advisories)Source: ENISA EUVD

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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Microchip Technology) lists Microchip Time Provider 4100 versions before 2.5.0 as affected. No release containing a fix is confirmed on record.

Use of Hard-coded Credentials vulnerability in Microchip Time Provider 4100 allows Malicious Manual Software Update.This issue affects Time Provider 4100: before 2.5.0.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 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.3%
EPSS %ILE
26th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: 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).

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

March 28, 2026

Last Modified

August 12, 2026

Advisory Details (1)

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

TIM Group | Vulnerability Research & Advisor

https://www.gruppotim.it/en/footer/TIM-red-team.html

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2025-9497?
CVE-2025-9497 is a critical-severity vulnerability; its CVE record was published on March 28, 2026. Use of Hard-coded Credentials vulnerability in Microchip Time Provider 4100 allows Malicious Manual Software Update.This issue affects Time Provider 4100: before 2.5.0.
When was CVE-2025-9497 made public?
CVE-2025-9497 was made public on March 28, 2026: that is the date its CVE record's CNA, Microchip Technology, gives for when the vulnerability was made public. The CVE record itself was published on March 28, 2026. EchelonGraph's copy of the record carries a last-modified date of August 12, 2026; the record at its source may have been updated since.
Is CVE-2025-9497 actively exploited?
CVE-2025-9497 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-9497?
CVE-2025-9497 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-9497?
No fix for CVE-2025-9497 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 CVE record's CNA (Microchip Technology) lists Microchip Time Provider 4100 versions before 2.5.0 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-9497?

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