Skip to main content
Mallory
HighVulnerability

CVE-2025-30513: Intel TDX Migration TOCTOU Privilege Escalation

Published Feb 10, 2026 · Updated 28 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.3High · v4
EPSS0.16%5th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-30513CWE-367

CVE-2025-30513 is a time-of-check to time-of-use race condition in the Intel Trust Domain Extensions (TDX) module's migration handling, identified in TDX 1.5. A malicious privileged host can change a Trust Domain's attributes from migratable to debuggable while its immutable state is being imported. This bypasses the intended isolation between the host and the confidential virtual machine, exposing the Trust Domain's entire decrypted state. Exploitation can occur after attestation, potentially exposing secrets provisioned after attestation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality and integrity of the affected Trust Domain, defeating its protection against an untrusted host. The host can access the entire decrypted state, potentially reconstruct another Trust Domain from that state, or perform live monitoring. Previously completed attestation does not prevent exploitation during a subsequent migration. No direct availability impact is identified for this CVE.

Mitigation

If you can’t patch tonight, do this now.

Until updates are deployed, restrict and monitor privileged local and hypervisor access, enforce least privilege for host administration, and reduce unnecessary administrative access to affected systems. These controls reduce opportunities for exploitation but do not restore Trust Domain isolation against an already malicious privileged host.

Remediation

Patch, then assume compromise.

Install the corrected Intel TDX module through the applicable Intel or platform-vendor updates associated with INTEL-SA-01397. The exact fixed TDX module version is not specified in the available information. For affected HPE StoreEasy Gen11 systems using U63 or U54 ROM families, install BIOS/firmware v2.80_01-29-2026 or later. For affected HPE SimpliVity systems, apply the relevant updated BIOS firmware and SimpliVity Gen11 Support Pack 2026-0605 or later. Plan deployment carefully because TDX module updates can disrupt running workloads where Trust Domain Preservation and Live Migration support is insufficient.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-30513 exploited in the wild?
As of Oct 21, 2026, Mallory has no reports of CVE-2025-30513 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-30513?
As of Oct 21, 2026, Mallory has found no public exploit for CVE-2025-30513.
Is there a patch for CVE-2025-30513?
Install the corrected Intel TDX module through the applicable Intel or platform-vendor updates associated with INTEL-SA-01397. The exact fixed TDX module version is not specified in the available information.
How severe is CVE-2025-30513?
CVE-2025-30513 has a CVSS v4 score of 8.3 (High) and an EPSS score of 0.16% (5th percentile) as of Oct 21, 2026.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
asusNews · May 18, 2026Security Update for ASUS GPU Servers – Third-Party Component VulnerabilitiesA third-party component vulnerability addressed by ASUS BIOS version 3003 / Secure Boot DBX Update 06102025 for affected ASUS GPU servers.Read more ↗the hacker newsNews · Feb 11, 2026Over 60 Software Vendors Issue Security Fixes Across OS, Cloud, and Network PlatformsOne of five reported vulnerabilities affecting Intel Trust Domain Extensions (TDX) 1.5; specific impact details are not provided in the content.Read more ↗support hpeNews · Feb 11, 2026HPESBHF05018 rev.1 - Certain HPE StoreEasy Servers Using Certain Intel Processors, INTEL-SA-01397, 2026.1 IPU, Intel Trust Domain Extensions (Intel TDX) module Advisory, Multiple VulnerabilitiesA locally exploitable vulnerability in Intel processors (Intel TDX module per INTEL-SA-01397) impacting certain HPE StoreEasy servers, with potential for privilege escalation and/or information disclosure/DoS.Read more ↗bughunters googleNews · Feb 10, 2026Strengthening the Foundation: A Joint Security Review of Intel TDX 1.5 - Google Bug HuntersA time-of-check to time-of-use vulnerability in Intel TDX 1.5 migration and Trust Domain lifecycle management allows a malicious host operator to convert a migratable Trust Domain into a debuggable one during immutable-state import. This exposes the entire decrypted TD state, defeating TDX confidentiality guarantees and enabling live monitoring or reconstruction of the TD. Exploitation can occur after attestation, when secrets are already present. Intel remediated the vulnerability through a TDX module update. The article announces proof-of-concept exploits for two disclosed vulnerabilities but does not identify which ones, so exploit availability for this specific CVE is unconfirmed.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.