CVE-2025-32007VulnerabilityPublished 10 Feb 2026

CVE-2025-32007: TDX · Information Disclosure

Affects TDXSource CVE Database V5

Not known to be exploited · CVSS 5.6 Medium · fixed in 1.5.24 : update TDX when convenient.

Data as of 26 Oct 2026, 07:57 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.
Patch: Available – fixed in 1.5.24

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: Present
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: 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: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
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 =before version tdx module 1.5.24	Fixed in–

AI-suggested

To mitigate CVE-2025-32007, European organizations should take the following specific actions: 1) Immediately verify the version of Intel TDX modules deployed and upgrade to version 1.5.24 or later where the vulnerability is fixed. 2) Restrict privileged local access strictly to trusted administrators and implement robust access control policies to minimize the risk of insider threats. 3) Employ continuous monitoring and auditing of privileged user activities to detect suspicious behavior that could indicate exploitation attempts. 4) Harden virtualization host security by applying the principle of least privilege and isolating management interfaces from general user access. 5) Coordinate with cloud service providers to confirm that underlying infrastructure is patched and secure if using third-party hosted environments. 6) Incorporate vulnerability scanning and compliance checks for TDX versions as part of regular security assessments. 7) Prepare incident response plans that include scenarios involving information disclosure from hypervisor-level vulnerabilities. These measures go beyond generic advice by focusing on controlling privileged access and ensuring timely patching in complex virtualized environments.

Description

Out-of-bounds read for some TDX before version tdx module 1.5.24 within Ring 0: Hypervisor may allow an information disclosure. Authorized adversary with a privileged user combined with a low 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.

Impact

For European organizations, the primary impact of CVE-2025-32007 is the potential unauthorized disclosure of sensitive information within virtualized environments that utilize Intel TDX technology. This is particularly critical for cloud service providers, data centers, and enterprises relying on hardware-based isolation for multi-tenant workloads. Confidentiality breaches could expose intellectual property, personal data subject to GDPR, or other sensitive corporate information, leading to regulatory penalties and reputational damage. Since the vulnerability requires privileged local access, the threat is heightened in environments where internal threat actors or compromised administrators exist. The lack of impact on integrity and availability reduces the risk of system disruption or data manipulation but does not diminish the seriousness of data leakage in regulated sectors such as finance, healthcare, and government. Additionally, the medium CVSS score suggests a moderate risk level, but the ease of exploitation by privileged users means that organizations must consider internal security controls and monitoring to prevent privilege escalation and lateral movement.

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, 16:50 UTC

Technical details

References

Community reviews

Related threats