CVE-2025-35973

MEDIUMPre-NVD 4.54.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.5 under a secondary CVSS source (NVD's own analysis pending). 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, secondary
Trending — Patch released this week
4.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.5Exploit: None knownExposed: 0

A fix is available — apply it.

Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal OS may allow an escalation of privilege. Authorized 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 require no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.

CVSS v3
4.5
EG Score
4.5(medium)
EG Risk
20(Track)
EG Risk 20/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
Severity45% × 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

August 12, 2026

Advisory Details (1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmicrocode_ctl-4:20260812-0.el10_22026-09-16redhat
redhatmicrocode_ctl-4:20260210-1.20260812.1.el9_82026-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

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
intel-ucode20260812-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
intel-ucode20260812-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
intel-ucode20260812-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
intel-ucode20260812-r0
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 24× in last 7d / 82× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-35973?
CVE-2025-35973 is a medium vulnerability published on August 11, 2026. Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal OS may allow an escalation of privilege. Authorized adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur…
When was CVE-2025-35973 disclosed?
CVE-2025-35973 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-35973 actively exploited?
CVE-2025-35973 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.0% of all scored CVEs.
What is the CVSS score of CVE-2025-35973?
CVE-2025-35973 has a CVSS v3 base score of 4.5 (NVD).
How do I remediate CVE-2025-35973?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-35973, 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-35973

Explore →

Is Your Infrastructure Affected by CVE-2025-35973?

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