Skip to main content
Mallory
MediumVulnerability

CVE-2026-20763: Local privilege escalation in Intel TDX Guest L2 vCPU entry

Published Aug 11, 2026 · Updated 6 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS4.6Medium · v4
EPSS0.15%4th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Intel Corporation
IdentifiersCVE-2026-20763CWE-682 · Incorrect Calculation

CVE-2026-20763 is an incorrect-calculation vulnerability in the Intel TDX Guest Rust package tdx-guest, affecting versions >=0.1.8 and <0.3.1. The tdx_guest::tdcall::enter_l2_vcpu() function computes the RCX operand for the TDG.VP.ENTER TDCALL but passes the raw l2_vm_idx instead. The intended operand encodes the L2 VM index in bits 53:52 and the translation-invalidation control in bits 1:0. The incorrect operand instead supplies a zero VM index field and causes the low bits of the supplied index to be interpreted as the invalidation control. A highly privileged local attacker may exploit this flaw to escalate privileges.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may cause privilege escalation, with low impacts to confidentiality, integrity, and availability of the vulnerable system. No confidentiality, integrity, or availability impacts to subsequent systems are identified. The vulnerability has a medium-severity CVSS 4.0 score of 4.6.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by restricting local access to affected systems, tightly limiting privileged user access, and minimizing opportunities for untrusted or less-trusted local users to interact with vulnerable Intel TDX Guest software components. Because the described attack involves a system software adversary combined with a privileged user, hardening administrative access paths and enforcing least privilege may reduce exploitability until the fixed version can be deployed.

Remediation

Patch, then assume compromise.

Upgrade tdx-guest to version 0.3.1 or later. The fix changes enter_l2_vcpu() to pass the computed RCX operand, encoding both the L2 VM index and translation-invalidation control, rather than the raw L2 VM index. Versions earlier than 0.1.8 are listed as unaffected.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Intel CorporationTrust Domain Extensions Guestapplication
FAQ

Frequently asked questions

Is CVE-2026-20763 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-20763 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-20763?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-20763.
Is there a patch for CVE-2026-20763?
Upgrade tdx-guest to version 0.3.1 or later. The fix changes enter_l2_vcpu() to pass the computed RCX operand, encoding both the L2 VM index and translation-invalidation control, rather than the raw L2 VM index.
What products are affected by CVE-2026-20763?
Intel Corporation Trust Domain Extensions Guest.
How severe is CVE-2026-20763?
CVE-2026-20763 has a CVSS v4 score of 4.6 (Medium) and an EPSS score of 0.15% (4th percentile) as of Nov 11, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.