CVE-2026-23660
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 · uneditedImproper access control in Azure Portal Windows Admin Center allows an authorized attacker to elevate privileges locally.
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 confidenceImproper access control in Azure Portal Windows Admin Center allows an authorized attacker to locally escalate privileges beyond their intended permission level. This local privilege escalation vulnerability stems from insufficient validation of user permissions, enabling a user with baseline access to gain elevated administrative rights on the system.
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< 2.6.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Windows Admin Center installationOpen PowerShell and run: Get-Service -Name 'WindowsAdminCenter*' or check for the service via Services.msc looking for 'Windows Admin Center'Affected if The service does not exist or is not installed, then the system is not affected
-
Determine installed versionOpen PowerShell and run: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows Admin Center' -ErrorAction SilentlyContinue).Version or check the version in Programs and Features for 'Windows Admin Center'Affected if The version is returned as a value less than 2.6.4, indicating the vulnerable version is installed
-
Confirm version comparisonCompare the discovered version number against the affected range: any version below 2.6.4 (such as 2.6.3, 2.5.0, 2.0, 1.x) is within the affected rangeAffected if The installed version is any release prior to 2.6.4, meaning the vulnerability is present in the environment
If Windows Admin Center is installed and the version is below 2.6.4, the environment is affected by this local privilege escalation vulnerability.
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 · scoped2.6.4
Apply vendor patches for Azure Portal Windows Admin Center and review role-based access control (RBAC) configurations to ensure the principle of least privilege is enforced. Verify that all authorized users have only the minimum permissions required for their functions.
Windows Admin Center 2.6.4
- 1. Identify current Windows Admin Center version by checking Programs and Features or using the WAC gateway endpoint
- 2. Download Windows Admin Center version 2.6.4 or later from the official Microsoft Download Center
- 3. Review the Windows Admin Center upgrade documentation on Microsoft Learn
- 4. Create a backup of your current Windows Admin Center configuration and settings
- 5. Perform the upgrade by running the installer for version 2.6.4 or later on the Windows Admin Center server
- 6. Verify the upgrade completed successfully by accessing Windows Admin Center and confirming functionality
- 7. Check that the version displayed shows 2.6.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23660 — 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-23660 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