CVE-2025-27940: TDX Module · Information Disclosure
Affects TDX ModuleSource CVE Database V5
Not known to be exploited · CVSS 5.6 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TDX Module | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Upgrade TDX Modules to version tdx1.5 or later as soon as Intel releases a patch or updated firmware addressing CVE-2025-27940. 2) Restrict and monitor privileged user access rigorously, employing least privilege principles and strong authentication to reduce the risk of local privileged attackers. 3) Employ host-based intrusion detection and behavioral monitoring to detect anomalous activities indicative of side channel exploitation attempts. 4) Isolate critical workloads and sensitive data from environments where privileged user compromise is more likely. 5) Maintain up-to-date inventory of systems using TDX technology to prioritize patching and risk assessment. 6) Collaborate with cloud providers to ensure their TDX implementations are patched and secure. 7) Conduct regular security audits and penetration testing focusing on privileged access controls and side channel attack vectors. These measures go beyond generic advice by focusing on the unique access requirements and attack complexity of this vulnerability.
Description
Out-of-bounds read for some TDX Module before version tdx1.5 within Ring 0: Hypervisor may allow an information disclosure. Software side channel 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 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.