CVE-2026-58544
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 · uneditedUse after free in Windows Management Services allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 use-after-free vulnerability in Windows Management Services allows a locally authenticated, authorized attacker to exploit improper memory handling after an object is freed, enabling local privilege escalation to higher privileges.
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< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2525< 10.0.26100.33158CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 build versionOpen PowerShell and run: [System.Environment]::OSVersion.Version or run 'winver' to see the full build number (e.g., 10.0.26100.8875)Affected if Build number is lower than 10.0.26100.8875 for Windows 11 24h2/Server 2025, lower than 10.0.26200.8875 for Windows 11 25h2, or lower than 10.0.28000.2525 for Windows 11 26h1
-
Confirm Windows Management Services is presentOpen PowerShell and run: Get-Service | Where-Object {$_.DisplayName -like '*Management*'} to list services containing 'Management' in the nameAffected if Windows Management Services or related management services are installed on the system
-
Verify service statusCheck if the Windows Management Services are in a Running or Started state using: Get-Service | Where-Object {$_.DisplayName -like '*Management*'} | Select-Object Name, StatusAffected if Any Windows Management Services are running, as the vulnerability requires the service to be active for exploitation
-
Check for pending security updatesRun: Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 to list recently installed patchesAffected if No recent security patches related to Windows Management Services have been applied, indicating the system may be unpatched for this vulnerability
System is affected if running a Windows 11 24h2/25h2/26h1 or Windows Server 2025 build below the specified thresholds AND Windows Management Services are present and active on the machine.
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.26100.887510.0.26100.3315810.0.26200.8875
Apply Microsoft security patches for Windows Management Services once available; prioritize rapid deployment of OS security updates. Until patch is available, limit local administrative access and monitor for unusual process behavior.
Windows 11 24h2 build 10.0.26100.8875+ | Windows 11 25h2 build 10.0.26200.8875+ | Windows 11 26h1 build 10.0.28000.2525+ | Windows Server 2025 build 10.0.26100.33158+
- Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Open Settings > Windows Update > Check for updates, or visit the Microsoft Update Catalog
- Locate and install the security update containing KB number that includes version 10.0.26100.8875 (24h2/Server 2025), 10.0.26200.8875 (25h2), or 10.0.28000.2525 (26h1)
- Restart the computer when prompted to complete the installation
- Verify the update was installed by checking Windows Update history or running 'winver' to confirm the build number meets the minimum version requirement
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58544 — 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-2026-58544 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