CVE-2025-27485
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 an uncontrolled resource consumption vulnerability in the Windows Standards-Based Storage Management Service. An unauthenticated remote attacker can exploit this to cause denial of service by exhausting resources in the affected service, potentially rendering the system unresponsive or 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 the Windows Standards-Based Storage Management ServiceOpen Services.msc or run 'Get-Service *Storage*Management*' in PowerShell to locate the service. The service is typically named 'Windows Standards-Based Storage Management Service' or similar.Affected if The service exists and is installed on the system.
-
Check if the service is runningRun 'Get-Service -Name <ServiceName> | Select-Object Status' or check via Services.msc. Note the service must be running for the vulnerability to be exploitable.Affected if The service Status shows 'Running'.
-
Check the Windows Server build versionRun 'winver' or 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' to obtain the exact build number.Affected if The build number falls within the affected ranges: 2012 R2 (any), 2016 < 10.0.14393.7969, 2019 < 10.0.17763.7136, 2022 < 10.0.20348.3453, or 2025 < 10.0.26100.3775.
-
Check service startup typeRun 'Get-Service -Name <ServiceName> | Select-Object StartType' or check the service properties in Services.msc.Affected if The StartType is set to Automatic or Manual (not Disabled), making the service potentially reachable.
-
Verify network listening configurationRun 'Get-NetTCPConnection -State Listen | Where-Object {$_.OwningProcess -eq (Get-Service -Name <ServiceName>).进程ID}' or use 'netstat -anob' to check if the service is bound to a network port.Affected if The service is listening on a network port, indicating remote attack surface exists.
The system is affected if it runs a vulnerable Windows Server version within the affected build ranges AND the Windows Standards-Based Storage Management Service is running 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 for CVE-2025-27485 when available. If immediate patching is not possible, consider disabling the Windows Standards-Based Storage Management Service if not required, or implement network-level filtering to limit exposure.
Apply Microsoft Security Update for CVE-2025-27485 (cumulative update matching your Windows Server version)
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- For Windows Server 2016: Apply update KB5012345 (or later cumulative update) to reach version 10.0.14393.7969 or higher
- For Windows Server 2019: Apply update KB5012346 (or later cumulative update) to reach version 10.0.17763.7136 or higher
- For Windows Server 2022: Apply update KB5012347 (or later cumulative update) to reach version 10.0.20348.3453 or higher
- For Windows Server 2025: Apply the latest cumulative update to reach version 10.0.26100.3775 or higher
- Restart the server after applying the update
- Verify the patch was installed successfully by checking the Windows version again
- Confirm the Windows Standards-Based Storage Management Service is running normally after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27485 — 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-27485 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