Notifications
Clear all
Topic starter
02/08/2026 12:07 pm
TL;DR: A token validation flaw in Azure Windows Admin Center let an attacker with local admin on one machine bypass identity checks, execute remote code, and move laterally across Azure VMs and Arc-connected systems in the same tenant, according to Cymulate Research Labs. The failure shows how scoped tokens and proof-of-possession controls collapse when user binding, request binding, and gateway assumptions are not enforced.
NHIMG editorial — based on content published by Cymulate: CVE-2026-20965 token validation flaw leading to tenant-wide RCE in Azure Windows Admin Center
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
Questions worth separating out
Q: What breaks when Azure AD SSO tokens are not tightly bound in cloud management tools?
A: The management plane can accept authorization context that does not belong to the same user, request, or resource, which lets a local foothold expand into cloud control.
Q: Why do cloud management tools create tenant-wide risk when authorization is validated poorly?
A: They sit at the point where local admin access meets tenant-scoped authority.
Q: What do organisations get wrong about proof-of-possession for tokens?
A: They often treat it as a narrow technical enhancement instead of a governance boundary.
Practitioner guidance
- Validate token-user-resource binding end to end Test whether the management service requires the same user principal, the same resource identifier, and the same request context before granting access.
- Audit management-plane exposure for direct IP and gateway bypass paths Check whether JIT rules expose the service through both the intended gateway and the underlying network interface.
- Instrument identity-based detections for anomalous admin reuse Correlate privileged access events with the machine being managed, the tenant boundary, and the historical role of the account.
What's in the full report
Cymulate's full blog covers the operational detail this post intentionally leaves for the source:
- The exact token fields and validation checks used by Windows Admin Center in Azure AD SSO flows.
- The exploitation walk-through showing how a local administrator can abuse the management path.
- The detection ideas for retrospective hunting across Azure logs and WAC activity.
- The updated Exposure Validation scenario used to test the vulnerability in customer environments.
👉 Read Cymulate's analysis of CVE-2026-20965 in Azure Windows Admin Center →
Azure WAC token validation flaws: what IAM teams need to know?
Explore further
02/08/2026 1:11 pm
Tenant-wide management trust is the real attack surface here. The flaw did not merely weaken authentication on one endpoint. It allowed a local administrator on one machine to inherit authority across the tenant because the management plane trusted token context more than it verified it. That is a cloud identity governance failure, not just a product defect. Practitioners should treat management channels as identity-critical infrastructure, because a single validation gap can bypass segmentation and collapse administrative boundaries.
A few things that frame the scale:
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: Who is accountable when a management-plane flaw exposes administrative access?
A: The owning platform team and the identity governance function share accountability, because the flaw spans application design and privileged access control. Management consoles should be governed like identity infrastructure, with clear ownership for redirect policy, token handling, session design, and secure update response when flaws are found.
👉 Read our full editorial: Token validation flaws in Azure WAC can break tenant isolation
