Skip to main content
VulnerabilityPublished

CVE-2025-32467: TDX Module · Information Disclosure

Affects TDX ModuleSource CVE Database V5

0

Not known to be exploited · CVSS 5.6 Medium.

Data as of 26 Oct 2026, 10:12 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 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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
TDX ModuleAffected
  • =before version tdx1.5
Fixed in–

AI-suggested

European organizations should implement the following specific mitigation steps: 1) Inventory and identify all systems running Intel TDX Modules prior to version tdx1.5 to understand exposure. 2) Apply vendor-supplied patches or firmware updates as soon as they become available to remediate the uninitialized variable flaw. 3) Restrict and monitor privileged user access rigorously, employing least privilege principles and strong authentication mechanisms to reduce the risk of local exploitation. 4) Employ runtime monitoring and anomaly detection to identify suspicious privileged activity that could indicate exploitation attempts. 5) Harden hypervisor and host OS configurations to minimize attack surface, including disabling unnecessary services and interfaces. 6) Conduct regular security audits and penetration testing focused on virtualization security to detect potential weaknesses. 7) Maintain up-to-date incident response plans that include scenarios involving insider threats and hypervisor-level compromises. These targeted actions go beyond generic advice by focusing on the specific conditions and environment of the vulnerability.

Description

Use of uninitialized variable for some TDX Module before version tdx1.5 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 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.

References

Community reviews

Loading reviews…