CVE-2025-27470
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 vulnerability in Windows Standards-Based Storage Management Service allows remote, unauthenticated attackers to cause denial of service by exhausting resources via network requests to the affected 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.
-
Identify Windows Server versionRun 'winver' command or check System Properties to obtain the exact Windows Server build number (for example, 10.0.17763.x for Server 2019)Affected if The installed version falls within the affected ranges: Server 2012 R2 (any), Server 2016 before build 14393.7969, Server 2019 before build 17763.7136, Server 2022 before build 20348.3453, or Server 2025 before build 26100.3775
-
Locate the Standards-Based Storage Management ServiceOpen Services console (services.msc) and locate 'Windows Standards-Based Storage Management Service', or run 'Get-Service *Storage*' in PowerShellAffected if The service exists on the system (this service is included in Windows Server installations with the Storage Management feature available)
-
Verify if the service is runningIn Services console, check the Status column for the Windows Standards-Based Storage Management Service, or run 'Get-Service -Name 'sMSS' in PowerShellAffected if The service Status is Running - the vulnerability is only exploitable when the service is active
-
Assess network exposure of the serviceCheck firewall rules and service listening ports. Run 'netsh interface tcp show global' and review if the service is bound to accessible network interfaces. The service typically uses port 5985 (HTTP) or 5986 (HTTPS) for WS-ManagementAffected if The service is listening on a reachable network interface (not localhost-only) and firewall rules permit inbound access from untrusted networks
A system is affected if it runs a vulnerable Windows Server version, has the Windows Standards-Based Storage Management Service installed and running, and the service is network-accessible to remote attackers.
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 Microsoft security updates for this vulnerability through Windows Update or manually download the patch from Microsoft Update Catalog.
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
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- Confirm the build number matches the vulnerable versions listed in the CVE (< 10.0.14393.7969 for Server 2016, < 10.0.17763.7136 for Server 2019, < 10.0.20348.3453 for Server 2022, < 10.0.26100.3775 for Server 2025)
- For Windows Server 2016/2019/2022/2025: Apply the latest Windows Updates via Settings > Update & Security > Windows Update, or use Windows Server Update Services (WSUS)
- Alternatively, download and install the cumulative update corresponding to the fixed build number from the Microsoft Update Catalog
- Verify the patch installed successfully by checking the build number after restart
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27470 — 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-27470 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