CVE-2025-54512

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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, secondary
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

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

A DLL hijacking vulnerability within the AMD Ryzen Master installation could allow a local user-privileged attacker to escalate privileges, potentially resulting in arbitrary code execution.

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

Published

August 11, 2026

Last Modified

August 12, 2026

References (1)

Vendor Advisories for CVE-2025-54512(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 26× in last 7d / 42× 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-08-20 22:54 UTCEPSS rescore
  2. 2026-08-20 21:23 UTCGHSA enrichment
  3. 2026-08-20 08:35 UTCGHSA enrichment
  4. 2026-08-19 19:47 UTCEG score recompute
  5. 2026-08-19 19:47 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 06:59 UTCGHSA enrichment
  8. 2026-08-18 18:10 UTCEG score recompute
  9. 2026-08-18 18:10 UTCGHSA enrichment
  10. 2026-08-18 13:47 UTCEPSS rescore
  11. 2026-08-18 05:21 UTCGHSA enrichment
  12. 2026-08-17 16:29 UTCEG score recompute
  13. 2026-08-17 16:29 UTCGHSA enrichment
  14. 2026-08-17 13:46 UTCEPSS rescore
  15. 2026-08-17 03:26 UTCEG score recompute
  16. 2026-08-17 03:26 UTCGHSA enrichment
  17. 2026-08-16 14:55 UTCEPSS rescore
  18. 2026-08-16 14:38 UTCEG score recompute
  19. 2026-08-16 14:38 UTCGHSA enrichment
  20. 2026-08-16 02:13 UTCEPSS rescore
  21. 2026-08-16 01:50 UTCGHSA enrichment
  22. 2026-08-15 13:02 UTCEG score recompute
  23. 2026-08-15 13:02 UTCGHSA enrichment
  24. 2026-08-15 01:29 UTCEPSS rescore
  25. 2026-08-15 00:14 UTCGHSA enrichment
Show 17 more
  1. 2026-08-14 11:26 UTCGHSA enrichment
  2. 2026-08-13 22:38 UTCEG score recompute
  3. 2026-08-13 22:38 UTCGHSA enrichment
  4. 2026-08-13 21:59 UTCEPSS rescore
  5. 2026-08-13 09:50 UTCGHSA enrichment
  6. 2026-08-12 21:02 UTCGHSA enrichment
  7. 2026-08-12 14:24 UTCEG score recompute
  8. 2026-08-12 14:24 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-12 13:25 UTCEG score recompute
  12. 2026-08-12 13:25 UTCGHSA enrichment
  13. 2026-08-12 07:26 UTCGHSA enrichment
  14. 2026-08-11 18:37 UTCEG score recompute
  15. 2026-08-11 18:37 UTCGHSA enrichment
  16. 2026-08-11 17:37 UTCEG score recompute
  17. 2026-08-11 17:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-54512?
CVE-2025-54512 is a high vulnerability published on August 11, 2026. A DLL hijacking vulnerability within the AMD Ryzen Master installation could allow a local user-privileged attacker to escalate privileges, potentially resulting in arbitrary code execution.
When was CVE-2025-54512 disclosed?
CVE-2025-54512 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-54512 actively exploited?
CVE-2025-54512 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.0% of all scored CVEs.
What is the CVSS score of CVE-2025-54512?
CVE-2025-54512 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2025-54512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-54512, 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-54512

Explore →

Is Your Infrastructure Affected by CVE-2025-54512?

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

Start Free Scan →Browse All CVEs