Skip to main content
VulnerabilityPublished Updated

CVE-2026-20763: Tdx guest · `enter_l2_vcpu` passes the wrong RCX operand to `TDG.VP.ENTER`

Affects tdx-guestSource GCVE Database

0
Compare
Authoritative record:CVE-2026-20763· Medium 4.6

Not known to be exploited · CVSS 4.6 Medium : upgrade to 0.3.1 when convenient.

Data as of 11 Nov 2026, 10:32 UTC

CVSS 4.0 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.3.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 10 Nov 2026.

What to do

Upgrade tdx-guest to 0.3.1.

Affected software

ProductAffectedFixed in
crates.iotdx-guestpkg:cargo/tdx-guestOther threatsAffected
  • >=0.1.8 <0.3.1
Fixed in
  • 0.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and was released in tdx-guest version 0.3.1. Users should upgrade to version 0.3.1 or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in the tdx-guest component causes the function enter_l2_vcpu to pass an incorrect RCX operand to the TDG.VP.ENTER TDCALL. This results in the TDX module receiving a VM index of 0 and misinterpreting invalidation control bits, potentially leading to escalation of privilege. The issue has a CVSS 4.0 base score of 4.6 (medium severity). It was fixed in version 0.3.1 by correcting the RCX value calculation.

References

Community reviews

Loading reviews…