Skip to main content
CVE-2025-20613VulnerabilityPublished

CVE-2025-20613: Intel(R) TDX · Information Disclosure

Affects Intel(R) TDXSource CVE Database V5

0

Not known to be exploited · CVSS 2.0 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  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 2026-10-26.

What to do

AI-suggested

1. Restrict local access: Limit the number of users with authenticated local access to systems running Intel TDX to reduce the attack surface. 2. Monitor and audit: Implement enhanced monitoring and auditing of local user activities on TDX-enabled systems to detect any suspicious behavior indicative of exploitation attempts. 3. Firmware updates: Stay in close contact with Intel for firmware or microcode updates addressing this vulnerability and apply patches promptly once available. 4. Isolate sensitive workloads: Where possible, segregate highly sensitive workloads into environments with stricter access controls and additional layers of security beyond TDX. 5. Use complementary security controls: Employ additional encryption and data protection mechanisms at the application or OS level to mitigate potential information disclosure risks from firmware vulnerabilities. 6. Vendor engagement: Engage with cloud service providers or hardware vendors to confirm their mitigation plans and timelines for this vulnerability in their Intel TDX deployments. 7. Incident response readiness: Prepare incident response plans that include scenarios involving local authenticated attackers exploiting firmware weaknesses to ensure rapid containment and remediation.

Description

Predictable Seed in Pseudo-Random Number Generator (PRNG) in the firmware for some Intel(R) TDX may allow an authenticated user to potentially enable information disclosure via local access.

References

Community reviews

Loading reviews…