Quick answers
- Is CVE-2026-63027 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63027 being exploited in the wild.
- How severe is CVE-2026-63027?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Intel TDX Migration Trust Domain (MigTD).
- Is there a fix for CVE-2026-63027?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-63027 attacked?
- It is attacked from the adjacent network, in device firmware.
- Am I affected by CVE-2026-63027?
- Check whether you run Intel TDX Migration Trust Domain (MigTD). Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the get_tcb_level_by_svn function within MigTD's Ring 0 hypervisor code, where an incorrect behavior order allows improper handling of trusted computing base (TCB) level lookups. The flaw can be triggered via adjacent network access without authentication or special privileges. An attacker can exploit this to crash or hang the hypervisor, causing denial of service to dependent virtual machines.
Affected products
- Intel TDX Migration Trust Domain (MigTD)
Timeline
- 2026-11-10: disclosed