CVE-2025-31936

MEDIUMNVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

Score 5.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. NVD baseline CVSS 5.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-210690 (ENISA EUVD) · GHSA-v7w9-9v5r-766h (GitHub Security Advisories)Source: ENISA EUVD

5.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processors when using Intel(R) TDX within SMM may allow an escalation of privilege. SMM adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
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 (5.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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, and whom BOD 26-04 binds: 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).

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.

The score's inputs: 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

Advisory Details (1)

Auto-updated Aug 11, 2026
Patch available.
Web page

INTEL-SA-01379

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01379.html

Vendor Advisories for CVE-2025-31936(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmicrocode_ctl-4:20260210-1.20260812.1.el9_82026-09-16redhat
redhatmicrocode_ctl-4:20260812-0.el10_22026-09-16redhat
redhatmicrocode_ctl-4:20260812-1.el8_102026-09-08redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:65147

Frequently asked(5)

What is CVE-2025-31936?
CVE-2025-31936 is a medium-severity vulnerability; its CVE record was published on August 11, 2026. Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processors when using Intel(R) TDX within SMM may allow an escalation of privilege. SMM adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result…
When was the CVE record for CVE-2025-31936 published?
The CVE record for CVE-2025-31936 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-31936 actively exploited?
CVE-2025-31936 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-31936?
CVE-2025-31936 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2025-31936?
A fix for CVE-2025-31936 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-31936 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-31936?

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

Book a Demo →Browse All CVEs