Skip to main content

Intel TDX MigTD CVE-2026-61887

CRITICAL
Missing Critical Step in Authentication (CWE-304)
2026-11-10 intel
9.4
CVSS 4.0 · Vendor: intel
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacent-network position to MigTD
  2. Delivery
    Initiate SPDM rebind exchange
  3. Exploit
    Bypass missing authentication step
  4. Execution
    Impersonate trusted migration peer
  5. Impact
    Execute code / disclose TD data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Critical step enforcement
Exploitation Conditions

Requires the target host to be running the Intel TDX Migration Trust Domain (MigTD) and performing (or reachable for) SPDM rebind during Trust Domain migration - the vulnerable step is the missing authentication check in the MigTD SPDM rebind implementation. The attacker needs ADJACENT network access (AV:A): a logically adjacent position such as the same migration network segment or an adjacent host path, not arbitrary Internet reach. Per the CVSS vector no authentication (PR:N), no user interaction (UI:N), and no special attack requirements (AT:N) are needed, and complexity is low (AC:L). The primary limiting factor is reachability: exploitation is constrained to adjacent access against hosts actively using TDX MigTD migration, which bounds real-world exposure despite the maximal impact metrics.

Impact

This is a genuine high-priority issue, not a high-CVSS/low-real-risk artifact, but its urgency rests on severity and vendor signaling rather than confirmed exploitation. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N) describes an unauthenticated, low-complexity attack with no user interaction and no special attack requirements, and the impact is maximal - high confidentiality, integrity and availability on both the vulnerable MigTD system and subsequent systems (SC:H/SI:H/SA:H), consistent with a scope-changing compromise of a trust-domain migration component. CWE-304 (missing critical step in authentication) in the SPDM rebind path aligns with an authentication-bypass leading to escalation of privilege, information disclosure and potential RCE. Two tempering factors: the attack vector is ADJACENT (AV:A), not fully remote-over-Internet, so an attacker needs a logically adjacent position (same L2 segment / migration network / co-resident host path) rather than arbitrary Internet reach - the description's phrase 'Network adversary ... remote code execution ... potentially occur via adjacent access' conflates network and adjacent language, so treat reachability as adjacent-network, not open-Internet. EPSS is not provided, there is no CISA KEV listing, and no public exploit is referenced; the 'act_now' label is the vuln.today priority signal and the report originates from Intel, not from confirmed in-the-wild activity. Net: prioritize patching for any TDX-migration deployment, but recognize exploitation is currently theoretical and gated by adjacent access.

Exploit ScenarioDerived

An attacker positioned on the migration/adjacent network path to a host running Intel TDX MigTD initiates or intercepts an SPDM rebind exchange and exploits the missing authentication step to impersonate a legitimate peer. Because no authentication, privileges, or user interaction are required and complexity is low, the attacker can escalate privilege, disclose Trust Domain data, and potentially achieve remote code execution within the MigTD context. No public exploit is identified at time of analysis, so this scenario is inferred from the CWE-304 authentication-bypass class and the CVSS adjacent/low-complexity metrics rather than from demonstrated exploit code.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 10, 2026

Missing authentication in the Intel TDX Migration Trust Domain (MigTD) SPDM rebind path allows an unauthenticated attacker on an adjacent network to escalate privileges, disclose information and potentially achieve remote code execution on hosts engaged in Trust Domain migration. The flaw is scored 9.4 under CVSS 4.0 and carries a scope-change vector (AV:A/AC:L/PR:N/UI:N/S:C) with high confidentiality, integrity and availability impact to the vulnerable component and to subsequent systems. No public exploit code or CISA KEV entry is associated with it at time of analysis, and the priority label is act_now; the practical limit on exposure is reachability, since the attacker must sit on a logically adjacent path to a host that is actively using MigTD migration.

RemediationAI

No fixed version or workaround is listed in the supplied data, so no patch version can be cited here; the authoritative fix information is Intel advisory intel-sa-01580 at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html, which should be checked for the corrected MigTD release and any Intel-supplied mitigation, and a patched MigTD build should be deployed on every host participating in TDX migration. Because the deficiency sits inside the SPDM rebind handshake itself rather than in an optional feature that can be turned off, the practical lever is reachability: the independent assessment fixes the attack at AV:A, so confining the migration network path to trusted peers and segments bounds who can reach the rebind flow, at the cost of making cross-site or multi-tenant migration topologies harder to operate and slower to reconfigure. That network restriction is a compensating measure for limited exposure only, not a substitute for the vendor fix, and the priority label is act_now, so remediation should proceed on a current patching cycle.

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 Intel TDX Migration Trust Domain, the component that moves a Trust Domain between hosts while preserving its protected state, and it sits in the Ring 0 / hypervisor layer of the platform per the supplied description. The affected code is the SPDM (Security Protocol and Data Model) rebind implementation - the DMTF-defined handshake used for device attestation and session key establishment, whose rebind step re-establishes that binding when a TD is migrated to a new host. The root cause is classified as CWE-304, Missing Critical Step in Authentication, meaning an authentication step that should occur during the rebind sequence is absent, so the peer's identity is not properly verified before the flow proceeds. The supplied CPE entry (cpe:2.3:a:n/a:intel(r)_tdx_migration_trust_domain_(migtd)) carries a placeholder vendor and no version bounds, and the sources do not describe how the missing check is reached at the packet or protocol-exchange level, so the trigger is not described in the available sources; the scope-change rating reflects that a failure inside the migration path can propagate beyond the vulnerable component to the host and the migrating domain.

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

Vendor (intel) PRIMARY 9.4 CRITICAL
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 9.6 CRITICAL

Adjacent access gives AV:A; no auth or interaction per PR:N/UI:N; subsequent-system impacts (SC/SI/SA:H) justify S:C with full C/I/A loss.

3.1 AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (intel).

CVSS VectorVendor: intel

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

Missing critical step in authentication in the MigTD SPDM rebind implementation for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an escalation of privilege and information disclosure. Network adversary with an unauthenticated user combined with a low complexity attack may enable remote code execution. 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 (high) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (high) impacts.

Executive ViewAI

Why It Matters

CVE-2026-61887 is a critical missing authentication flaw in Intel TDX Migration Trust Domain (MigTD) that lets an unauthenticated attacker on an adjacent network compromise hosts during Trust Domain migration. Because successful exploitation can lead to full loss of confidentiality, integrity, and availability-including potential remote code execution-organizations using Intel TDX migration for confidential computing face material risk to sensitive workloads and trust boundaries.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting migration traffic to trusted network segments, enforcing strong network authentication and encryption for SPDM sessions, disabling or limiting MigTD live migration where feasible, and monitoring for unauthorized adjacent-network access to TDX hosts.

Threat Intelligence Overview

Prevalence
Low
Niche Intel TDX confidential-computing migration component, only in TDX-enabled datacenter hosts
Data Quality
2 sources
Confidence: Low

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +47
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)CVE.org

cpe:2.3:a:n/a:intel(r)_tdx_migration_trust_domain_(migtd):*:*:*:*:*:*:*:*

More in N A

View all
CVE-2024-51092 CRITICAL POC
9.1 May 08

LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr

CVE-2025-15684 MEDIUM POC
5.5 Aug 12

Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han

CVE-2024-45257 HIGH POC
7.3 May 08

A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi

CVE-2025-15687 LOW POC
2.1 Aug 12

Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc

CVE-2025-15686 LOW POC
2.1 Aug 12

Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula

CVE-2025-67888 HIGH POC
7.3 May 08

Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root

CVE-2024-53326 HIGH POC
7.3 May 08

LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(

CVE-2026-38360 CRITICAL POC
9.8 May 08

Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti

CVE-2026-30623 CRITICAL POC
9.8 Jul 15

Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr

CVE-2026-67917 CRITICAL POC
9.8 Aug 17

SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg

CVE-2026-75337 CRITICAL POC
9.8 Aug 27

Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ

CVE-2026-31072 CRITICAL POC
9.8 May 19

Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy