CVE-2026-60071Intel(R) TDX Migration Trust Domain (MigTD) unchecked quantity
CVE-2026-60071 is a unchecked quantity in Intel(R) TDX Migration Trust Domain (MigTD), rated medium (6.7 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Awaiting Analysis
What it is
A count or size from input is not checked before it is used.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, with an administrator account, and nobody has to click anything.
What an attacker gains
A successful attack can take it offline. In practice, this kind of flaw lets an attacker drive the component into behaviour its authors did not intend.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place Intel(R) TDX Migration Trust Domain (MigTD) runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Limit who can run code or sign in on the hosts that run it.
Description from NVD
Improper validation of specified quantity in input in the MigTD vsock packet handling for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable denial of service. 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 (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Interfaces that accept external input. The flaw sits at the input boundary of the affected component.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.
Questions to answer about your own systems
- Where does Intel(R) TDX Migration Trust Domain (MigTD) run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.