RCE in Microsoft Azure Attestation and Device Health Attestation can impact widely used Azure cloud services and trust flows across enterprises.
CVE-2026-71331
Integer overflow in Azure Attestation allows remote code execution.
Is CVE-2026-71331 being exploited?
Not confirmed. CVE-2026-71331 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. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-71331?
CVE-2026-71331 is rated High with a CVSS score of 8.1. 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-71331?
Yes. A fix has been recorded for CVE-2026-71331. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71331 affect?
CVE-2026-71331 affects Microsoft Azure Attestation Service, Microsoft Device Health Attestation Service, Azure tenant attestation workflows. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71331?
Apply Microsoft patch ASAP; restrict access to attestation endpoints and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution over network via integer overflow in Azure Attestation/Device Health Attestation, enabling arbitrary code execution and compromise of attestation flows.
Immediate action required
- affected>= 10.0.17763.0 and < 10.0.17763.9121
- affected>= 10.0.17763.0 and < 10.0.17763.9121
- affected>= 10.0.17763.0 and < 10.0.17763.9121
- affected>= 10.0.20348.0 and < 10.0.20348.5499
- affected>= 10.0.26100.0 and < 10.0.26100.33296
- affected>= 10.0.26100.0 and < 10.0.26100.33296
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.