CVE-2025-27572VulnerabilityPublished 10 Feb 2026

CVE-2025-27572: TDX · Information Disclosure

Affects TDXSource CVE Database V5

Not known to be exploited · CVSS 5.6 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.6Medium

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

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

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

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: None: There is no loss of integrity within 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 2026-10-26.

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 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	Affected =See references	Fixed in–

AI-suggested

Organizations should implement strict access controls to limit privileged user accounts and monitor for unusual privileged activity within TDX-enabled environments. Applying vendor patches or microcode updates as soon as they become available is critical. Until patches are released, consider isolating TDX workloads on dedicated hardware or restricting access to trusted administrators only. Employ runtime monitoring and anomaly detection to identify potential exploitation attempts. Additionally, review and harden hypervisor configurations to minimize attack surface. For cloud providers, segregate tenant workloads and enforce strict privilege separation. Regularly update threat intelligence feeds and coordinate with Intel advisories for emerging mitigation techniques. Finally, conduct security audits focusing on privileged access management and transient execution attack vectors.

Description

Exposure of sensitive information during transient execution for some TDX within Ring 0: Hypervisor may allow an information disclosure. Authorized adversary with a privileged user combined with a high complexity attack may enable data exposure. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Impact

For European organizations, the primary impact is the potential exposure of sensitive data in virtualized environments leveraging Intel TDX technology. This could include confidential business information, cryptographic keys, or personal data processed within virtual machines protected by TDX. Since the vulnerability requires privileged local access, the risk is heightened in environments where multiple tenants or administrators share infrastructure, such as cloud service providers or large enterprises using virtualization for workload isolation. The confidentiality breach could lead to compliance violations under GDPR if personal data is exposed. However, the lack of integrity or availability impact limits the scope to data leakage rather than system disruption. The medium severity suggests a moderate risk that should be addressed proactively, especially in sectors handling sensitive or regulated data.

Summary

CVE-2025-27572 is an information disclosure vulnerability found in Intel's Trusted Domain Extensions (TDX), specifically within the Ring 0 hypervisor layer. The flaw arises from transient execution mechanisms that can leak sensitive information under certain conditions. An attacker with privileged local access (e.g., administrative or root level) and the ability to execute a complex attack can exploit this vulnerability to extract confidential data from the hypervisor environment. The attack does not require user interaction and does not need special internal knowledge beyond privilege, but it is considered high complexity due to the nature of transient execution exploitation. The vulnerability affects confidentiality with no direct impact on integrity or availability. The CVSS 4.0 score is 5.6 (medium), reflecting local attack vector, high attack complexity, no user interaction, and high confidentiality impact. No patches or exploits are currently publicly available, but the vulnerability highlights risks in TDX environments where hypervisor isolation is critical for security.

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 10 Feb 2026, 17:01 UTC

Technical details

References

Community reviews

Related threats