Intel TDX MigTD
CVE-2026-57892
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network position to MigTD host
-
DeliverySend crafted migration/policy traffic
-
ExploitExploit insufficient policy granularity
-
ExecutionBypass access control decision
-
PersistEscalate privilege into Trust Domain
-
ImpactCompromise confidentiality and integrity of subsequent system
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V8 - Authorization Insufficient granularity of access control
|
| Exploitation Conditions | Exploitation requires the target to be running the Intel TDX Migration Trust Domain (MigTD) v2 with its policy evaluation engine active - i.e., an Intel TDX confidential-computing deployment using TD migration. The attacker must be on an adjacent network (AV:A), not the open internet, so network positioning on the same logical segment/broadcast domain as the host is a hard prerequisite. No authentication (PR:N) and no user interaction (UI:N) are needed, but the attack is high-complexity (AC:H), meaning the trigger is non-trivial; the specific mechanism of the insufficient-granularity flaw is not described in the available sources. Limiting factors: adjacency requirement, high attack complexity, and the narrow population of hosts actually running MigTD v2. |
| Impact | This is a genuine but conditional priority rather than a drop-everything emergency. The CVSS 4.0 vector (AV:A/AC:H/AT:N/PR:N/UI:N) scores 8.8 and describes an unauthenticated adjacent-network attacker needing a high-complexity attack path to escalate privilege within the MigTD, with a confirmed scope change into the subsequent system (VC:H/VI:H and SC:H/SI:H). The vuln.today decision label is 'this_week', which aligns with a serious-but-not-active rating. No EPSS score, CISA KEV listing, or POC/exploit reference is present in the input, so there is no evidence of active exploitation or public exploit code. The main tension is between high impact (confidentiality and integrity high on both the vulnerable and subsequent systems) and real-world difficulty: AC:H plus adjacent-only access (AV:A, not AV:N) materially constrains who can reach the target. Net: treat as a prioritized patch for environments running Intel TDX confidential computing with MigTD, but the adjacency requirement and high attack complexity reduce the likelihood of widespread opportunistic exploitation versus targeted attacks against confidential-computing infrastructure. |
| Exploit ScenarioDerived | An attacker positioned on the same adjacent network segment as the confidential-computing host sends crafted traffic that exploits insufficient granularity in the MigTD v2 policy evaluation engine, causing the policy check to under-restrict an action and yielding privilege escalation that breaches the confidentiality and integrity of the Trust Domain migration path. The attack requires no authentication and no user interaction but is high-complexity (AC:H), implying a non-trivial, carefully engineered trigger. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 10, 2026
Insufficient access-control granularity in the MigTD v2 policy evaluation engine within Intel TDX's Migration Trust Domain allows a network adversary positioned on an adjacent network to achieve privilege escalation inside the Ring 0 (hypervisor) layer, with high confidentiality and integrity impact extending to subsequent systems. Exploitation requires the target to be running Intel TDX with MigTD v2 and its policy evaluation engine active, and while no authentication or user interaction is needed, the attack is rated high complexity and the specific trigger mechanism is not described in the available sources. No public exploit code or PoC reference was identified at time of analysis and the vulnerability is not in CISA KEV; the vendor advisory is Intel SA-01580.
RemediationAI
No vendor-released patch or exact fixed version is identified in the available data, so the primary action is to consult Intel Security Advisory SA-01580 (https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html) for Intel's fixed version or updated MigTD release and apply it as directed. Because exploitation requires adjacency, the most directly applicable compensating control is to restrict the network segment on which TD migration traffic and MigTD policy exchange occur, so that only known migration peers on the same logical segment/broadcast domain can reach the host - the trade-off is that migration topologies must be re-planned and legitimate peer addresses explicitly enumerated. Organisations that do not currently require live TD migration can reduce exposure by not running the MigTD v2 policy evaluation engine on hosts where migration is not needed, accepting the loss of migration capability. These measures reduce exposure but do not repair the insufficient access-control granularity itself; the vendor fix remains the complete resolution. Track the advisory for the patched release, since the available intelligence lists none.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Intel TDX (Trust Domain Extensions) is Intel's confidential-computing architecture in which workloads run inside hardware-isolated Trust Domains managed by a TDX Module, and the Migration Trust Domain (MigTD) is the component responsible for securely migrating those trust domains between hosts. The flaw is classified as CWE-1220 (Insufficient Granularity of Access Control), meaning the policy evaluation engine in MigTD v2 does not distinguish access rights finely enough, so a policy check that should have separated privilege levels can be satisfied in a way that grants broader authority than intended; the result, per Intel, is that the hypervisor (Ring 0) may allow an escalation of privilege. The CVSS:4.0 vector (AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N) and the independent CVSS:3.1 assessment (AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N) both describe an adjacent-network, unauthenticated, no-interaction, high-complexity attack with scope change and high confidentiality/integrity but no availability impact. The CPE string identifies Intel(R) TDX Migration Trust Domain (MigTD) with no version bound recorded, and the evidence does not explain the concrete conditions or input needed to trigger the policy-engine flaw.
Know when Intel R Tdx Migration Trust Domain Migtd gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Adjacent-only reach gives AV:A, the described non-trivial trigger gives AC:H, no auth gives PR:N, and the subsequent-system impact maps to S:C with C:H/I:H and no availability loss.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
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.
Executive ViewAI
Intel TDX's MigTD v2 policy engine contains a high-severity access-control flaw that could allow an attacker on an adjacent network to escalate privileges to the hypervisor layer, compromising confidentiality and integrity of migrated workloads and potentially spreading to other systems. Organizations using Intel TDX for confidential computing face a moderate risk because exploitation requires a specialized environment and high attack complexity, but the lack of a patch means affected systems remain exposed until mitigations are applied.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to TDX hosts and migration channels, disable MigTD v2 policy evaluation if not essential, monitor for unauthorized policy changes, and follow Intel SA-01580 guidance.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Affected Products (CPE)CVE.org
Missing authentication in the Intel TDX Migration Trust Domain (MigTD) SPDM rebind path allows an unauthenticated attack
Authentication bypass in the Intel TDX Migration Trust Domain (MigTD) rebinding protocol allows a privileged local adver
Capture-replay authentication bypass in Intel TDX Migration Trust Domain (MigTD) lets a local, highly privileged system-
Information disclosure in Intel's TDX Migration Trust Domain (MigTD) lets a network-reachable adversary read data that s
Privilege escalation and information disclosure in Intel TDX MigTD stem from an expired-pointer dereference in the virti
Write-what-where in the Intel TDX Migration Trust Domain (MigTD) lets a privileged local adversary who already holds Rin
Privilege escalation in Intel TDX's Migration Trust Domain (MigTD) allows an adversary who already controls the Ring 0 h
Privilege escalation in the Intel TDX Migration Trust Domain (MigTD) signing path allows a privileged local system-softw
A denial-of-service condition exists in Intel's TDX Migration Trust Domain (MigTD), where the GetQuote routine contains
Use-after-free in the MigTD virtio driver, a Ring 0 component of the Intel TDX Migration Trust Domain used during trust-
Local information disclosure in Intel MigTD, the Intel TDX Migration Trust Domain component operating in the Ring 0/hype
Integrity-only privilege escalation in the SPDM responder of Intel's TDX Migration Trust Domain (MigTD), caused by incom
NVD
CVE.org
GitHub PoC
Exploit-DB