CVE-2025-55231Network attack vector

Remote code execution via storage race condition

Published Aug 21, 2025 · Updated Feb 26, 2026

A race condition in Microsoft Windows Server allows remote attackers to execute code through Storage-based Management Service network requests. The service permits concurrent execution against a shared resource without required synchronization; Microsoft has not disclosed the resource or request path. Exploitation requires no prior privileges but has high complexity and requires interaction by a target user; success grants code execution on the server.

CVSS severity7.5
High
EPSS probability0.48%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A race condition in Microsoft Windows Server allows remote attackers to execute code through Storage-based Management Service network requests. The service permits concurrent execution against a shared resource without required synchronization; Microsoft has not disclosed the resource or request path. Exploitation requires no prior privileges but has high complexity and requires interaction by a target user; success grants code execution on the server.

The record

CVE
CVE-2025-55231
Published
Aug 21, 2025
Updated
Feb 26, 2026
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-362, T1203
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 21, 2025CVE publishedPublication date reported by the CVE source.
  2. Feb 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.17763.0 <10.0.17763.7558

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.7558
Microsoft · Windows Server 2025 (Server Core installation)version=10.0.26100.0 <10.0.26100.4652
Microsoft · Windows Server 2016 (Server Core installation)version=10.0.14393.0 <10.0.14393.8246
Microsoft · Windows Server 2016version=10.0.14393.0 <10.0.14393.8246
Microsoft · Windows Server 2012 R2 (Server Core installation)version=6.3.9600.0 <6.3.9600.22676
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.7558
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.3932
Microsoft · Windows Server 2025version=10.0.26100.0 <10.0.26100.4652
Microsoft · Windows Server 2012 R2version=6.3.9600.0 <6.3.9600.22676

Published CVSS scores

7.5MicrosoftCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo