CVE-2025-54510

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

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

A missing lock verification in AMD Secure Processor (ASP) firmware may permit a locally authenticated attacker with administrative privileges to alter MMIO routing on some Zen 5-based products, potentially compromising guest system integrity.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

April 16, 2026

Last Modified

April 17, 2026

References (1)

Vendor Advisories for CVE-2025-54510(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 5× in last 7d / 26× 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.

Showing the most recent 100 of 181 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-54510?
CVE-2025-54510 is a medium vulnerability published on April 16, 2026. A missing lock verification in AMD Secure Processor (ASP) firmware may permit a locally authenticated attacker with administrative privileges to alter MMIO routing on some Zen 5-based products, potentially compromising guest system integrity.
When was CVE-2025-54510 disclosed?
CVE-2025-54510 was first published in the National Vulnerability Database on April 16, 2026, with the most recent update on April 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-54510 actively exploited?
CVE-2025-54510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2025-54510?
CVE-2025-54510 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-54510?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-54510, 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-54510

Explore →

Is Your Infrastructure Affected by CVE-2025-54510?

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

Start Free Scan →Browse All CVEs