Missing critical step in authentication in the MigTD SPDM rebind implementation for the Intel(R) TDX Migration Trust Domain (MigTD) within…
Affects the SPDM rebind implementation in Intel(R) TDX Migration Trust Domain (MigTD). CVSS rates it 9.4 critical, and no vendor severity or fix is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The facts do not list a workaround or mitigation. Check Intel's advisory for guidance on limiting exposure while no fix is available.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The facts do not list a workaround or mitigation. Check Intel's advisory for guidance on limiting exposure while no fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-61887 (Missing critical step in authentication in the MigTD SPDM rebind implementation for the Intel(R) TDX Migration Trust Domain (MigTD) within…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-61887 (entry last updated 2026-11-10): Affected: - n/a Intel(R) TDX Migration Trust Domain (MigTD): version range not reported Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Affects the MigTD SPDM rebind implementation (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: adjacent access, no login, no user action. CISA KEV: CVE-2026-61887 is not listed as of cve.now's last read. This KEV status is for CVE-2026-61887 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html - https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-61887 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-61887.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- n/a Intel(R) TDX Migration Trust Domain (MigTD)
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-61887
Is CVE-2026-61887 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The MigTD SPDM rebind implementation is missing a critical authentication step. The reported impact is that the hypervisor may gain escalation of privilege and information disclosure.Source: intel.com
Am I affected, and how do I check?
The issue affects the MigTD SPDM rebind implementation. The facts do not list specific versions or ranges, so check whether your MigTD deployment uses SPDM rebind against Intel's advisory for the affected versions.Source: intel.com
How do I fix CVE-2026-61887?
The facts do not name a fixed version, so no upgrade target is given. Check Intel's advisory for an updated MigTD release that addresses this issue.Source: intel.com
What if there's no patch?
The facts do not list a workaround or mitigation. Check Intel's advisory for guidance on limiting exposure while no fix is available.Source: intel.com