CVE-2025-62626

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th 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
7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation0.2% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

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

November 21, 2025

Last Modified

June 17, 2026

References (1)

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-06-08ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-06-08ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-06-08ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-06-08ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-06-08ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-06-08ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20251202.1 (61 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20251202.1 (61 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20251202.1 (61 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20250311.1~deb12u1 (60 versions)
  • every version up to 3.20251202.1: fixed in 3.20251202.1
—

Weakness Classification(1)

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

All Vendor Advisories

(20)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 26× 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 88 of 184 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. 12 repeat rows among the latest 100 are merged into the row they repeat. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-62626?
CVE-2025-62626 is a high-severity vulnerability; its CVE record was published on November 21, 2025. Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.
When was CVE-2025-62626 made public?
CVE-2025-62626 was made public on November 21, 2025: 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 November 21, 2025. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-62626 actively exploited?
CVE-2025-62626 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-62626?
CVE-2025-62626 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-62626?
A fix for CVE-2025-62626 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-62626

Explore →

Is Your Infrastructure Affected by CVE-2025-62626?

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

Book a Demo →Browse All CVEs