Skip to content
Fencer Vulns
high 7.5

CVE-2025-55231 json

Windows Storage-based Management Service Remote Code Execution Vulnerability

published 2025-08-21 14 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-25494

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Storage allows an unauthorized attacker to execute code over a network.

Patch / fix

  • Microsoft Windows Server 2012 R2 6.3.9600.22676
  • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.22676
  • Microsoft Windows Server 2016 10.0.14393.8246
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.8246
  • Microsoft Windows Server 2019 10.0.17763.7558
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.7558
  • Microsoft Windows Server 2022 10.0.20348.3932
  • Microsoft Windows Server 2025 10.0.26100.4652
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.4652

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012 R2 (Server Core installation)
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.