VulnerabilityPublished 10 Feb 2026Updated 26 Feb 2026

CVE-2025-30513: TDX Module · Escalation of Privilege

Affects TDX ModuleSource CVE Database V5

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

8.4High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
TDX Module	Affected =See references	Fixed in–

AI-suggested

To mitigate CVE-2025-30513, organizations should: 1) Monitor Intel's security advisories closely and apply patches or firmware updates for the TDX Module as soon as they become available. 2) Restrict privileged user access rigorously, employing the principle of least privilege to minimize the number of users who can operate at the system software or hypervisor level. 3) Implement enhanced logging and monitoring of hypervisor-level activities to detect unusual or unauthorized privilege escalation attempts. 4) Use hardware-based security features and secure boot mechanisms to ensure integrity of the hypervisor and TDX components. 5) Conduct regular security audits and vulnerability assessments focused on virtualization infrastructure. 6) Consider network segmentation and isolation of critical virtualized workloads to limit the blast radius of any potential compromise. 7) Educate system administrators about the risks of race conditions and the importance of timely patch management in virtualization environments. These steps go beyond generic advice by emphasizing proactive access control, monitoring, and preparation pending patch availability.

Description

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.

Impact

The primary impact of CVE-2025-30513 is on the confidentiality and integrity of systems running the vulnerable TDX Module. Successful exploitation enables an attacker with privileged user access to escalate privileges within the hypervisor environment, potentially gaining unauthorized access to sensitive data or the ability to alter critical system operations. This can undermine the security guarantees of virtualization and trusted execution environments, leading to data breaches or compromise of multiple virtual machines hosted on the same physical hardware. Although availability is not directly affected, the loss of confidentiality and integrity at the hypervisor level can have cascading effects on organizational security posture, compliance, and trustworthiness of cloud or virtualized services. Organizations relying on Intel TDX for hardware-based isolation and security may face increased risk of insider threats or compromised system software components. The lack of known exploits in the wild currently limits immediate widespread impact, but the vulnerability remains a significant threat if weaponized.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01397.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 07:18 UTC

Technical details

References

Community reviews

Related threats