Intel MigTD
CVE-2026-56432
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain privileged hypervisor/Ring-0 access on TDX host
-
DeliveryInvoke MigTD signing via confused-deputy path
-
ExploitCoerce trusted component to sign/authorize operation
-
ExecutionSubvert migration trust domain integrity
-
ImpactCompromise protected guest integrity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
|
| Exploitation Conditions | Exploitation requires the attacker to already be a privileged system-software adversary at the Ring-0/hypervisor level on a host running Intel TDX with the Migration Trust Domain (MigTD) in use, and to reach the MigTD signing path to trigger the confused-deputy behavior (CWE-441). Per the CVSS vector this is local access only (AV:L), demands high existing privileges (PR:H), needs no user interaction (UI:N), and has low attack complexity with no special attack requirements (AC:L/AT:N). Limiting factors: it is not remotely exploitable and not usable by an unprivileged user - it is confined to hosts that deploy Intel TDX confidential computing and MigTD-based migration, so systems not using TD migration are not exposed. The exact internal trigger within the signing flow is not described in the available sources. |
| Impact | This is a locally-exploitable privilege-escalation flaw (CWE-441, confused deputy) in the MigTD signing path of Intel TDX Migration Trust Domain. The supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N, base 8.2) shows the key limiting factor clearly: exploitation requires LOCAL access and already-HIGH privileges (PR:H) - a system-software adversary operating at the Ring-0/hypervisor level - so this is not a remote, unauthenticated, or internet-scannable issue. What elevates the score despite those constraints is impact: integrity is high on both the vulnerable system (VI:H) and a subsequent system (SI:H/SC:H), meaning a compromised hypervisor can subvert the trust guarantees the migration domain is meant to protect, defeating the confidentiality/integrity promise of confidential computing. On exploitation signals: no CISA KEV listing, no public PoC, and no EPSS value were provided, so there is no public exploit identified at time of analysis - the only signals are the vendor advisory (Intel SA-01580) and the vuln.today 'this_week' priority. The 'this_week' decision label plus an 8.2 base is consistent with a real-but-not-emergency priority: patch on a normal expedited cycle rather than drop-everything. Net: a genuine security-boundary break for Intel TDX operators, but gated behind an attacker who already holds privileged local/hypervisor control, which narrows the realistic threat population to malicious or compromised host operators. |
| Exploit ScenarioDerived | A malicious or compromised hypervisor-level actor on a host running Intel TDX abuses the MigTD signing path so that the trusted migration component acts on the attacker's behalf (confused deputy), authorizing or signing a migration-related operation it should not. This lets the privileged host subvert the integrity of the migration trust domain and the protected guest, undermining the confidential-computing boundary. No public PoC is identified, and exploitation requires existing privileged local access, so this is a post-compromise / malicious-operator scenario rather than a drive-by attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 10, 2026
Privilege escalation in the Intel TDX Migration Trust Domain (MigTD) signing path allows a privileged local system-software adversary at the Ring-0/hypervisor level to abuse confused-deputy behavior and expand integrity and confidentiality impact across the TDX trust boundary. The flaw affects hosts running Intel TDX confidential computing with MigTD-based migration enabled; it is local-only, requires high existing privileges, and no public exploit code or KEV-listed active exploitation was identified at time of analysis. CVSS 8.2 reflects high integrity impact and scope change, not remote reachability.
RemediationAI
Consult Intel advisory SA-01580 for fixed MigTD or TDX versions and deployment-specific remediation, because the supplied data does not list an exact fix version and does not confirm that a patched build is available. Until a vendor fix is confirmed and applied, reduce exposure by ensuring MigTD-based TD migration is enabled only on hosts where Ring-0/hypervisor administrators are fully trusted, since exploitation requires high local privileges and access to the MigTD signing path; disabling or removing TD migration on less-trusted hosts limits exposure but may break live migration and confidential-computing workflows. Validate any such mitigation against the Intel advisory, as the available data does not confirm an alternative control.
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
The root cause is CWE-441, an unintended proxy or intermediary condition commonly called a confused deputy, in the MigTD signing flow for Intel TDX Migration Trust Domain. MigTD is part of Intel TDX confidential-computing migration; the vulnerability sits in Ring 0/hypervisor context and may let a privileged system-software adversary cause a signing operation to act under unintended authority. The provided CVSS:4.0 vector is AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N, and the independent assessment is CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N, both indicating local access, high privileges, no user interaction, and scope change rather than remote exploitability. The exact internal trigger within the MigTD signing flow is not described in the available sources, and hosts that do not use Intel TDX with MigTD migration are not exposed by this path.
Know when N A 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:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N
Local access by an already-privileged hypervisor actor (AV:L/PR:H), low complexity; integrity-only impact crossing the trust boundary into a subsequent system forces S:C with C:H/I:H and A:N.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Unintended proxy or intermediary ('confused deputy') in the MigTD signing for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local 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 (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.
Executive ViewAI
CVE-2026-56432 is a high-severity privilege escalation in Intel TDX Migration Trust Domain (MigTD) signing path that enables a privileged local adversary (Ring-0/hypervisor) to compromise the integrity and confidentiality of confidential computing workloads across trust boundaries. Organizations relying on Intel TDX for workload isolation-such as those in finance, healthcare, or government-are affected, undermining the assurance that sensitive data remains protected from infrastructure-level threats. Leadership should prioritize this vulnerability because it directly erodes the foundational trust of confidential computing deployments, potentially leading to data breaches and regulatory non-compliance.
No vendor-released patch identified at time of analysis; interim mitigations include disabling MigTD-based migration if possible, restricting Ring-0/hypervisor access to trusted administrators, monitoring for suspicious privileged activity, and applying any mitigations recommended by Intel's advisory.
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
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
NVD
CVE.org
GitHub PoC
Exploit-DB