Quick answers
- Is CVE-2026-20775 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-20775 being exploited in the wild.
- How severe is CVE-2026-20775?
- Medium severity, with a CVSS score of 5.3, published 11 August 2026.
- Which products and versions are affected?
- Intel 4th Gen Xeon Scalable processor 1.5.28 and earlier; Intel 5th Gen Xeon Scalable processor 1.5.28 and earlier; Intel Xeon 6 processor with P-cores 2.0.16 and earlier; Intel Xeon 6 SoC 2.0.16 and earlier.
- Is there a fix for CVE-2026-20775?
- 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-20775 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-20775?
- Check whether you run Intel 4th Gen Xeon Scalable processor, Intel 5th Gen Xeon Scalable processor, Intel Xeon 6 processor with P-cores or one of the others listed at an affected version. 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
This vulnerability is an uncaught exception (improper error handling) in Intel TDX modules running in Ring 0 (the highest privilege level). The flaw exists in 4th Gen, 5th Gen Intel Xeon Scalable processors, and Intel Xeon 6 processors with P-cores and SoC variants. A system software adversary with high privileges can trigger the exception via local access to cause a denial of service. The attack requires high complexity and privileged access (PR:H) but no user interaction. Intel has released firmware mitigations; users should update to the latest TDX module version provided by their system manufacturer.
Affected products
- Intel 4th Gen Xeon Scalable processor 1.5.28 and earlier
- Intel 5th Gen Xeon Scalable processor 1.5.28 and earlier
- Intel Xeon 6 processor with P-cores 2.0.16 and earlier
- Intel Xeon 6 SoC 2.0.16 and earlier
Timeline
- 2026-08-11: disclosed: CVE-2026-20775 published in INTEL-SA-01436