CVE-2025-30513

HIGHNVD 7.97.9—
EchelonGraph scoreMEDIUM confidence

Score 7.9 from GitHub Security Advisory (severity: HIGH) published 2026-02-10. NVD baseline CVSS 7.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Race condition for some TDX Module within Ring 0: Hypervisor may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not 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
7.9
EG Score
7.9(medium)
EPSS
2.4%
KEV
Not listed

Published

February 10, 2026

Last Modified

April 15, 2026

Advisory Details (1)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

INTEL-SA-01397

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

Vendor Advisories for CVE-2025-30513(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 / 40× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-30513?
CVE-2025-30513 is a high vulnerability published on February 10, 2026. Race condition for some TDX Module within Ring 0: Hypervisor may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements…
When was CVE-2025-30513 disclosed?
CVE-2025-30513 was first published in the National Vulnerability Database on February 10, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-30513 actively exploited?
CVE-2025-30513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-30513?
CVE-2025-30513 has a CVSS v3 base score of 7.9 (NVD).
How do I remediate CVE-2025-30513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-30513, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2025-30513?

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

Start Free Scan →Browse All CVEs