Intel TDX MigTD
CVE-2026-63027
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network access to migration fabric
-
ExploitSend crafted input to MigTD
-
ExecutionTrigger incorrect ordering in get_tcb_level_by_svn
-
ImpactDisrupt Migration Trust Domain availability
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incorrect behavior order
|
| Exploitation Conditions | Exploitation requires adjacent-network access (AV:A) to a host running the Intel TDX Migration Trust Domain (MigTD), the component that handles live migration of Trust Domains in Intel TDX confidential computing; the flaw lies in the get_tcb_level_by_svn routine. No authentication (PR:N) and no user interaction (UI:N) are needed, and no special attack requirement applies (AT:N), so default MigTD deployments are reachable by an on-fabric adversary. Limiting factors: the attacker must be positioned on the adjacent network/migration fabric rather than the open internet, the product is only present where Intel TDX with Trust Domain migration is deployed, and impact is restricted to availability (denial of service) with no data exposure or code execution. The precise trigger within get_tcb_level_by_svn is not described in the available sources beyond the CWE-696 incorrect-behavior-order classification. |
| Impact | Signals converge on a moderate, availability-only issue rather than a top priority. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N) describes an adjacent-network, low-complexity, unauthenticated attack with no attack requirements and no user interaction, but impact is confined to availability (VA:L) with no confidentiality or integrity effect and no subsequent-system impact (SC/SI/SA:N), yielding a base score of 5.3 (Medium). The vuln.today decision label is 'this_month' - meaning remediate on a routine patch cycle, not emergency. There is no CISA KEV listing, no EPSS score supplied, and no public exploit or PoC reference in the input, so exploitation remains theoretical. The adjacent (AV:A) rather than network (AV:N) vector is a meaningful limiter: an attacker needs to be on the same logical adjacent network/fabric as the MigTD, not arbitrary internet reach. No signals conflict; the main gap is the absence of an EPSS probability and any confirmation of exploitability, so prioritization rests on severity and the vendor advisory alone. |
| Exploit ScenarioDerived | An adversary with adjacent-network access to the migration fabric of an Intel TDX confidential-computing host sends crafted input that reaches the get_tcb_level_by_svn routine in MigTD, where an incorrect ordering of operations (CWE-696) can be driven to disrupt the Migration TD and deny service. No authentication or user interaction is required (PR:N/UI:N), and complexity is low (AC:L). No public exploit code or PoC reference is identified in the available data, so this is a plausible but unproven scenario. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 10, 2026
Adjacent-network attackers can degrade availability of Intel TDX Migration Trust Domain (MigTD), the component that handles live migration of Trust Domains in Intel TDX confidential computing, through incorrect ordering of operations in the get_tcb_level_by_svn routine. The flaw is reachable without authentication (PR:N) and without user interaction (UI:N) from the migration fabric, but impact is limited to availability (A:L) with no confidentiality or integrity effect and no code execution. Exposure is confined to environments where Intel TDX with Trust Domain migration is actually deployed, and no public exploit has been identified at time of analysis; priority is assessed as this-month rather than emergency.
RemediationAI
The only vendor reference supplied is Intel advisory intel-sa-01580 (https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html); no fixed MigTD build number is identified in the available data, so patch availability and the exact remediated version must be confirmed against that advisory before scheduling rollout, and the assessed priority is this-month rather than emergency. Because the issue is limited to availability under adjacent-network access, updating MigTD is the primary corrective action once Intel publishes the fixed build. No specific workarounds are documented in the provided sources; the most direct exposure reduction available from the deployment model is that environments which do not enable Intel TDX Trust Domain migration do not run MigTD and are therefore out of scope, so disabling TD migration where it is not operationally required removes the attack surface, at the cost of losing live-migration capability for confidential workloads.
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
MigTD is the migration trust domain used by Intel TDX to migrate confidential Trust Domains between hosts while preserving their protection; the affected routine, get_tcb_level_by_svn, derives a platform TCB level from a Security Version Number during that migration flow, and the defect is classified as CWE-696 (Incorrect Behavior Order), meaning a step in that sequence executes in the wrong order relative to its prerequisites. The issue sits in Ring 0/hypervisor context, so it is a platform-component logic flaw rather than an application-layer bug, and it maps to an availability-only outcome (VA:L) under the assessed vector AV:A/AC:L/PR:N/UI:N/S:U. The available sources do not describe the precise trigger inside get_tcb_level_by_svn beyond the CWE-696 classification, so the specific input or state that produces the denial of service is not confirmed; the CPE entry for the affected package is recorded with an unset vendor field, reflecting that the product is distributed as part of Intel TDX platform enablement rather than as a conventional standalone application.
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:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Adjacent, low-complexity, unauthenticated DoS with no user interaction maps to AV:A/AC:L/PR:N/UI:N; impact is availability-only (A:L) with no confidentiality or integrity effect and unchanged scope.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Incorrect behavior order in the get_tcb_level_by_svn for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow a denial of service. Network adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. 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 (none), integrity (none) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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-
Insufficient access-control granularity in the MigTD v2 policy evaluation engine within Intel TDX's Migration Trust Doma
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
NVD
CVE.org
GitHub PoC
Exploit-DB