CVE-2025-26652
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUncontrolled resource consumption in Windows Standards-Based Storage Management Service allows an unauthorized attacker to deny service over a network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Denial of Service vulnerability in Windows Standards-Based Storage Management Service stemming from uncontrolled resource consumption. An unauthenticated remote attacker can exploit this by sending specially crafted network requests to cause the service to consume excessive resources, rendering it unavailable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= r2< 10.0.14393.7969< 10.0.17763.7136< 10.0.20348.3453< 10.0.26100.3775CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Windows Server versionRun 'winver', 'systeminfo', or use PowerShell: Get-ComputerInfo | Select-Object WindowsVersion, OsVersionAffected if Version is Windows Server 2012 R2, or 2016 (build < 10.0.14393.7969), 2019 (build < 10.0.17763.7136), 2022 (build < 10.0.20348.3453), or 2025 (build < 10.0.26100.3775)
-
Locate Windows Standards-Based Storage Management ServiceRun PowerShell: Get-Service -Name StorSvc or open services.msc and search for 'Windows Standards-Based Storage Management Service'Affected if Service named 'StorSvc' exists on the system
-
Check if StorSvc service is runningRun PowerShell: Get-Service -Name StorSvc | Select-Object Status, StartTypeAffected if Service status is 'Running' and the Windows version falls within the affected ranges listed above
System is affected if it runs an unpatched Windows Server version within the affected range AND has the StorSvc service enabled and running, exposing the service to network-based resource exhaustion attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.14393.796910.0.17763.713610.0.20348.3453
Apply the Microsoft security update for CVE-2025-26652 to all affected Windows systems. If immediate patching is not possible, consider network segmentation or firewall rules to limit exposure to the Windows Standards-Based Storage Management Service.
Apply the corresponding Microsoft security update (KB) for your Windows Server version from the CVE-2025-26652 advisory on msrc.microsoft.com
- Identify the current Windows Server version and build number by running 'winver' or 'systeminfo'
- Open Windows Update by running 'ms-settings:windowsupdate' or use Windows Server Update Services (WSUS)
- Check for and install the appropriate security update for this vulnerability. The KB number can be found in the Microsoft Security Response Center advisory (msrc.microsoft.com) for CVE-2025-26652
- After installing the update, restart the server as prompted to apply the fix
- Verify the fix was applied successfully by checking that the build number matches or exceeds: Windows Server 2016: 10.0.14393.7969, Windows Server 2019: 10.0.17763.7136, Windows Server 2022: 10.0.20348.3453, Windows Server 2025: 10.0.26100.3775
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26652 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data