CVE-2025-27486
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 confidenceUncontrolled resource consumption in Windows Standards-Based Storage Management Service allows an unauthenticated remote attacker to trigger excessive resource usage (likely memory, CPU, or connections) by sending specially crafted network requests, resulting in denial of service.
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.
-
Check Windows Server build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the build numberAffected if Build number is below 14393.7969 for Server 2016, 17763.7136 for Server 2019, 20348.3453 for Server 2022, or 26100.3775 for Server 2025 (or if running Server 2012 R2)
A system is affected if it runs a vulnerable Windows Server version (2012 R2, 2016 < build 14393.7969, 2019 < build 17763.7136, 2022 < build 20348.3453, or 2025 < build 26100.3775) AND has the Standards-Based Storage Management Service enabled and network-accessible.
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 addressing CVE-2025-27486 to affected Windows systems, or follow vendor guidance for mitigating uncontrolled resource consumption in the Standards-Based Storage Management Service.
Windows Server 2016: Build 10.0.14393.7969 or later | Windows Server 2019: Build 10.0.17763.7136 or later | Windows Server 2022: Build 10.0.20348.3453 or later | Windows Server 2025: Build 10.0.26100.3775 or later
- Open Windows Update on the affected server
- Check for available security updates
- Install the latest cumulative update that includes the fix for CVE-2025-27486
- Alternatively, manually download and install the specific security update from Microsoft Update Catalog for your Windows Server version
- Restart the server if prompted to complete the installation
- Verify the Windows Standards-Based Storage Management Service is running properly after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27486 — 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-27486 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