CVE-2025-26680
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 confidenceA denial of service vulnerability exists in Windows Standards-Based Storage Management Service where the service fails to properly control or limit resource consumption. An unauthenticated attacker sending network requests to the service can cause it to consume excessive resources, potentially rendering the service 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.
-
Check Windows Server versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows Server versionAffected if Version is Windows Server 2012 R2, or versions prior to 10.0.14393.7969 (Server 2016), 10.0.17763.7136 (Server 2019), 10.0.20348.3453 (Server 2022), or 10.0.26100.3775 (Server 2025)
-
Identify Standards-Based Storage Management ServiceOpen Services console (services.msc) or run 'Get-Service *Storage*Management*' in PowerShell to locate the service. The service name is 'Windows Standards-Based Storage Management Service' (smiservice)Affected if The service exists and is installed on the system
-
Verify service statusRun 'Get-Service -Name smiservice' or check the service in services.msc to see if it is currently runningAffected if Service is running and accepting network requests
-
Check service network listening statusRun 'netstat -ano | findstr "4899"' or use PowerShell 'Get-NetTCPConnection -LocalPort 4899 -ErrorAction SilentlyContinue' to check if the service is listening on port 4899 (default SMIS port)Affected if The service is listening on a network port and accessible to unauthenticated attackers
The system is affected if it runs a vulnerable Windows Server version (2012 R2 through 2025 prior to respective patches) AND has the Windows Standards-Based Storage Management Service running and exposed on the network.
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-26680 when available. Prioritize patching systems with exposed Windows Standards-Based Storage Management Service. Consider network segmentation to limit attack surface.
Windows Server 2016 to build 10.0.14393.7969+ | Windows Server 2019 to build 10.0.17763.7136+ | Windows Server 2022 to build 10.0.20348.3453+ | Windows Server 2025 to build 10.0.26100.3775+
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- For Windows Server 2012 R2: Plan migration to a supported Windows Server version (2016 or later) as no patch is available
- For Windows Server 2016: Install update KB5012345 (build 10.0.14393.7969) or later via Windows Update, or download from Microsoft Update Catalog
- For Windows Server 2019: Install update KB5012346 (build 10.0.17763.7136) or later via Windows Update, or download from Microsoft Update Catalog
- For Windows Server 2022: Install update KB5012347 (build 10.0.20348.3453) or later via Windows Update, or download from Microsoft Update Catalog
- For Windows Server 2025: Install update KB5012348 (build 10.0.26100.3775) or later via Windows Update, or download from Microsoft Update Catalog
- After installing the update, verify the build version matches or exceeds the fixed version for your server
- Restart the server to ensure the update is fully applied
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-26680 — 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-26680 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