CVE-2025-0046

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: 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 (Advanced Micro Devices Inc.) lists AMD Power Design Manager (PDM) Software Installer for Windows versions 2026.1 as unaffected. No release containing a fix is confirmed on record.

Incorrect directory permissions could allow a local user to escalate their privileges, potentially resulting in arbitrary code execution.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
3rd
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 (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 11, 2026

Last Modified

September 29, 2026

Vendor Advisories for CVE-2025-0046(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 10× in last 7d / 71× 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 98 of 210 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 112 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-0046?
CVE-2025-0046 is a high-severity vulnerability; its CVE record was published on August 11, 2026. Incorrect directory permissions could allow a local user to escalate their privileges, potentially resulting in arbitrary code execution.
When was CVE-2025-0046 made public?
CVE-2025-0046 was made public on August 11, 2026: that is the date its CVE record's CNA, Advanced Micro Devices Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 11, 2026. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2025-0046 actively exploited?
CVE-2025-0046 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-0046?
CVE-2025-0046 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-0046?
No fix for CVE-2025-0046 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 (Advanced Micro Devices Inc.) lists AMD Power Design Manager (PDM) Software Installer for Windows versions 2026.1 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2025-0046 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-0046?

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