Evidence used
- CISA confirms exploitation in the wild.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 5.99% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-62215High confidence
Microsoft Windows Race Condition Vulnerability
Microsoft · Windows
7.0HighCVSS 3.1
Patch now
Patch availableCISA confirms exploitation in the wild and lists 2025-12-03 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 12 Nov 2025
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Microsoft Windows and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
CISA confirms exploitation in the wild and lists 2025-12-03 as the remediation due date.
Patch available01
What, why and how
Microsoft Windows Kernel contains a race condition vulnerability that allows a local attacker with low-level privileges to escalate privileges. Successful exploitation of this vulnerability could enable the attacker to gain SYSTEM-level access.
What
Microsoft Windows Kernel contains a race condition vulnerability that allows a local attacker with low-level privileges to escalate privileges. Successful exploitation of this vulnerability could enable the attacker to gain SYSTEM-level access.
Why
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Microsoft Windows Kernel contains a race condition vulnerability that allows a local attacker with low-level privileges to escalate privileges. Successful exploitation of this vulnerability could enable the attacker to gain SYSTEM-level access.
Why
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2025-11-12.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-362 ↗
CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8027
- Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.6575
- Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.6575
- Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6199
- Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6199
- Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.7171
- Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.7171
- Windows Server 2019: 10.0.17763.0 < 10.0.17763.8027
- Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8027
- Windows Server 2022: 10.0.20348.0 < 10.0.20348.4405
- Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.1965
- Windows Server 2025: 10.0.26100.0 < 10.0.26100.7171
- Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.7171
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 11 Nov 2025 · Last source change 26 Feb 2026, 16:57 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-93397
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/microsoft-security-advisory-november-2025-monthly-rollup-av25-739.secure@microsoft.com ↗
- Before
- remediation: cyber.gc.ca/microsoft-security-advisory-november-2025-monthly-rollup-av25-739 · vendor advisory: msrc.microsoft.com/CVE-2025-62215
- After
- vendor advisory: msrc.microsoft.com/CVE-2025-62215
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.17763.0 < 10.0.17763.8027; 10.0.19044.0 < 10.0.19044.6575; 10.0.19045.0 < 10.0.19045.6575; 10.0.22631.0 < 10.0.22631.6199; 10.0.26100.0 < 10.0.26100.7171; 10.0.26200.0 < 10.0.26200.7171 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8027; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.6575; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.6575; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6199; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6199; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.7171; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.7171; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8027; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8027; Windows Server 2022: 10.0.20348.0 < 10.0.20348.4405; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.1965; Windows Server 2025: 10.0.26100.0 < 10.0.26100.7171; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.7171 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Canadian Centre for Cyber Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Added to CISA KEV
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.