dbcve.org
Windows Admin CenterApplication · Microsoft

CVE-2026-58631

HIGH · 7.8 CVSS v3.1 Developing Published 2026-07-14
Fix available
A fix is available. Upgrade to 2606 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 5 weeks old

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 · unedited
Improper authorization in Windows Admin Center allows an authorized attacker to execute code locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

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 · low confidence

This is an improper authorization vulnerability in Windows Admin Center. An attacker who already has valid authorization credentials can bypass intended permission boundaries to execute code locally on the target system. The vulnerability stems from missing or insufficient authorization checks that should prevent authorized users from performing certain local code execution actions.

MitigationApply vendor-provided patches for Windows Admin Center when released. Review and restrict admin-level access accounts to principle of least privilege until the patch is available.

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
Windows Admin CenterApplication
Affected:< 2606

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Windows Admin Center installation
    Check for Windows Admin Center installation by looking in Program Files or via the Windows Admin Center installer. On the server, check the installation path (typically C:\Program Files\Windows Admin Center) or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Admin Center*"}'
    Affected if Windows Admin Center is installed on the system
  2. Determine installed version
    Open Windows Admin Center and navigate to the Settings > About page, or check the version in the installer. Alternatively, check the file version of 'Microsoft.WindowsAdminCenter.Client.dll' in the installation directory
    Affected if The installed version is lower than 2606 (for example, 2503, 2409, etc.)
  3. Confirm local code execution feature access
    Windows Admin Center enables remote management capabilities. Check if the 'Local Code Execution' or similar extension that allows running scripts/commands on the host is installed and enabled. Inspect the installed extensions via the Admin Center UI under 'Extensions'
    Affected if Local code execution extensions or scripts features are installed and accessible to standard users without proper authorization checks
  4. Review authorization configuration
    Inspect the Windows Admin Center user role assignments and permissions in the local 'msftadmincenter-users.json' configuration file or via the Admin Center under 'Users' settings
    Affected if Users with standard or limited permissions have access to features that should require elevated authorization

A system is affected if Windows Admin Center is installed with a version lower than 2606 and users with standard permissions can access local code execution features without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2606 or later
Fixed in 2606
Interim mitigation

Apply vendor-provided patches for Windows Admin Center when released. Review and restrict admin-level access accounts to principle of least privilege until the patch is available.

Recommended fix Moderate confidence

Windows Admin Center version 2606

  1. Review the official Microsoft Security Response Center (msrc.microsoft.com) advisory for CVE-2026-58631 for complete details
  2. Download Windows Admin Center version 2606 or later from the official Microsoft website
  3. Backup your current Windows Admin Center configuration
  4. Install the updated Windows Admin Center version 2606
  5. Verify the installation was successful and the version is 2606 or higher
  6. Test that Windows Admin Center functionality remains operational

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows Admin Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58631 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58631 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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