Infrastructure
CVE-2026-44685
Intel TDX MigTD auth bypass enables local hypervisor privilege escalation.
Major vulnerability. Hypervisor/CPU-level authentication bypass in Intel TDX MigTD can allow host/Ring0 takeover across cloud and enterprise virtualization — broadly impactful to infrastructure.
- CVSS
- 9.3Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- No score yet
- Fix
- Patch availablesee the advisories in the references
- Published
- 10 Nov 2026analysed here 12 Nov 2026
Summary
Impact
Local auth bypass in MigTD enables escalation to Ring 0 hypervisor code execution, allowing full host confidentiality/integrity/availability compromise.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Intel(R) TDX Migration Trust Domain (MigTD) | See referencesVendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Intel TDX (MigTD) hosts
- TDX-enabled hypervisors (Ring 0)
- Virtual machines on TDX hosts
- Cloud providers using Intel TDX
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
Timeline
- 10 Nov 2026Published
- 10 Nov 2026CVE record last updatedsame day later
- 12 Nov 2026Analysed by vulneraibility.com2 days later
Common questions
Is CVE-2026-44685 being exploited?
Not confirmed. CVE-2026-44685 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-44685?
CVE-2026-44685 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44685?
Yes. A fix has been recorded for CVE-2026-44685. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44685 affect?
CVE-2026-44685 affects Intel TDX (MigTD) hosts, TDX-enabled hypervisors (Ring 0), Virtual machines on TDX hosts, Cloud providers using Intel TDX. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44685?
Restrict local privileged access, apply Intel mitigations, update hypervisors and deploy vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Other links (1)
- intel.com /content/www/us/en/security-center/advisory/intel-sa-01580.html
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.