CVE-2026-96215: Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Autopil

Q: How do I fix CVE-2026-96215?

windows 11 24h2: upgrade to 10.0.26100.9711; windows 11 25h2: upgrade to 10.0.26200.9711; windows 11 26h1: upgrade to 10.0.28000.3231. Exact commands for each OS are on this page.

Q: Is CVE-2026-96215 being exploited?

CVE-2026-96215 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-96215 affect?

CVE-2026-96215 affects windows 11 24h2, windows 11 25h2, windows 11 26h1. Severity is high (CVSS 7.0). Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Autopilot allows an authorized attacker to elevate privileges locally.

Q: How urgent is CVE-2026-96215?

Priority 32/100. High severity; On your watchlist

Routine

HIGH 7.0WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-96215 is a high-severity flaw (CVSS 7.0) affecting windows 11 24h2, windows 11 25h2, windows 11 26h1. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Autopilot allows an authorized attacker to elevate privileges locally.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.0 (High)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-362
Published	2026-10-13
Last modified	2026-10-16

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-10-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-10-13 19:21 UTCPublished CVE record published
2026-10-16 14:59 UTCUpdated Record last modified

microsoft windows 11 24h2 UPGRADE

Affected: < 10.0.26100.9711

Fixed in: 10.0.26100.9711

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

microsoft windows 11 25h2 UPGRADE

Affected: < 10.0.26200.9711

Fixed in: 10.0.26200.9711

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

microsoft windows 11 26h1 UPGRADE

Affected: < 10.0.28000.3231

Fixed in: 10.0.28000.3231

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

microsoft windows 11 26h2 UPGRADE

Affected: < 10.0.26300.9711

Fixed in: 10.0.26300.9711

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-96215?

windows 11 24h2: upgrade to 10.0.26100.9711; windows 11 25h2: upgrade to 10.0.26200.9711; windows 11 26h1: upgrade to 10.0.28000.3231. Exact commands for each OS are on this page.

Is CVE-2026-96215 being exploited?

CVE-2026-96215 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-96215 affect?

CVE-2026-96215 affects windows 11 24h2, windows 11 25h2, windows 11 26h1. Severity is high (CVSS 7.0). Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Autopilot allows an authorized attacker to elevate privileges locally.

How urgent is CVE-2026-96215?

Priority 32/100. High severity; On your watchlist

Software pages

Windows vulnerabilities

Related CVEs

CVE-2026-69969 MEDIUM 4.7 UPGRADE UPGRADE Improper link resolution before file access ('link following') in Windows AppX Deployment Service allows an au
CVE-2026-69970 HIGH 7.0 UPGRADE UPGRADE Heap-based buffer overflow in Microsoft Streaming Service allows an authorized attacker to elevate privileges
CVE-2026-69971 MEDIUM 5.5 UPGRADE UPGRADE Incorrect authorization in Windows Kernel-Mode Drivers allows an authorized attacker to disclose information l
CVE-2026-69973 MEDIUM 6.5 UPGRADE UPGRADE Improper limitation of a pathname to a restricted directory ('path traversal') in Windows Libarchive allows an
CVE-2026-69974 MEDIUM 4.7 UPGRADE UPGRADE Out-of-bounds read in Desktop Window Manager allows an authorized attacker to disclose information locally.

References

← Back to latest CVEs