CVE-2025-27572: Information Disclosure in TDX
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.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
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.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Ireland, Italy, Spain, Poland
CVE-2025-27572: Information Disclosure in TDX
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.
AI-Powered Analysis
Technical Analysis
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.
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- intel
- Date Reserved
- 2025-04-15T21:18:07.419Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 698b5d5d4b57a58fa119cf3e
Added to database: 2/10/2026, 4:31:25 PM
Last enriched: 2/10/2026, 5:01:09 PM
Last updated: 2/21/2026, 12:19:41 AM
Views: 19
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.