CVE-2025-31936

MEDIUMNVD 5.75.7
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 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
Trending — Patch released this week
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: None knownExposed: 0

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

Published

August 11, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.

Patch Availability(3)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 36× in last 7d / 119× 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 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-31936?
CVE-2025-31936 is a medium vulnerability 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 CVE-2025-31936 disclosed?
CVE-2025-31936 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-31936 actively exploited?
CVE-2025-31936 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 99.2% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-31936, 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

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.