MIGTD · CVE-2026-57892 · Infrastructure
FIX → 0.7.2 ✓ verified
The MigTD v2 policy evaluation engine in Intel's TDX Migration Trust Domain does not restrict access finely enough, so a flaw in the hypervisor can allow privilege escalation. An attacker on an adjacent network with no credentials could read and modify confidential data of the affected system.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affects operators of Intel TDX confidential-computing hosts that use the MigTD reference software (live migration of trust domains), all versions before 0.7.2. The attacker needs adjacent network access and a high-complexity attack, but no credentials. Most application teams only inherit this through a cloud or hardware vendor; if you do not use TDX live migration you can skip it.
Who cares confidential-computing, hypervisor, intel-tdx, migtd
0.7.2 is affectedUpgrade to 0.7.2
Update Intel TDX Migration Trust Domain (MigTD) to version or later ().
Insufficient granularity of access control in the MigTD v2 policy evaluation engine for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an escalation of privilege. Network adversary with an unauthenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via adjacent access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
0.7.2NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.