Insufficient granularity of access control in the MigTD v2 policy evaluation engine for the Intel(R) TDX Migration Trust Domain (MigTD)…
Affects Intel TDX Migration Trust Domain (MigTD) deployments using the v2 policy evaluation engine. The checked facts list no fixed version, so no fix is confirmed yet.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts describe no workaround. Because the issue is tied to the v2 policy evaluation engine, the only related step they point to is limiting use of that engine, and they do not confirm that this reduces the risk.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Insufficient granularity of access control in the MigTD v2 policy evaluation engine for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an escalation of privilege. Network adversary with an unauthenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via adjacent 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 (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts describe no workaround. Because the issue is tied to the v2 policy evaluation engine, the only related step they point to is limiting use of that engine, and they do not confirm that this reduces the risk.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-57892 (Insufficient granularity of access control in the MigTD v2 policy evaluation engine for the Intel(R) TDX Migration Trust Domain (MigTD)…), 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-57892 (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): - Intel TDX Migration Trust Domain (MigTD) v2 policy evaluation engine in use (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: adjacent access, no login, no user action. CISA KEV: CVE-2026-57892 is not listed as of cve.now's last read. This KEV status is for CVE-2026-57892 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-57892 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-57892.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n/a Intel(R) TDX Migration Trust Domain (MigTD)
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-57892
Is CVE-2026-57892 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: cve.now feed data
What does this mean?
The v2 policy evaluation engine in MigTD does not apply access control with enough granularity. The facts say this can allow an escalation of privilege, with high confidentiality and integrity impact on the vulnerable system.Source: intel.com
Am I affected, and how do I check?
The issue concerns Intel TDX Migration Trust Domain (MigTD) when the v2 policy evaluation engine is in use. The checked facts give no version ranges, so check whether your MigTD setup uses the v2 policy engine.Source: intel.com
How do I fix CVE-2026-57892?
The checked facts name no fixed version or upgrade target. Check Intel's security advisory for MigTD for the fixed release and installation guidance.Source: intel.com
What if there's no patch?
The checked facts describe no workaround. Because the issue is tied to the v2 policy evaluation engine, the only related step they point to is limiting use of that engine, and they do not confirm that this reduces the risk.Source: intel.com