Skip to main content

Microsoft 365 Admin Center CVE-2026-62873

| EUVDEUVD-2026-54326 CRITICAL
Improper Verification of Cryptographic Signature (CWE-347)
2026-08-07 secure@microsoft.com GHSA-c89r-fxpx-x3w6
9.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach M365 Admin Center over network
  2. Delivery
    Forge token with tampered claims
  3. Exploit
    Bypass signature verification (CWE-347)
  4. Execution
    Service accepts forged identity
  5. Persist
    Elevate to administrative privileges
  6. Impact
    Control tenant resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
Exploitation Conditions

Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no special conditions are required beyond network reachability to the Microsoft 365 Admin Center service - no authentication, no privileges, and no user interaction. The concrete prerequisite implied by CWE-347 and the 'JWT Attack' tag is the ability to submit a crafted token/message whose signature the service fails to validate correctly; the attacker must be able to reach the portal's token-accepting endpoint over the network. Limiting factors are minimal given the vector: exploitation is bounded mainly by whatever network/Conditional-Access restrictions a tenant places in front of the admin portal and by Microsoft's server-side remediation, since this is a hosted service rather than a customer-deployed build. Authentication requirement is confirmed unauthenticated from PR:N in the provided vector.

Impact

The signals are largely aligned toward high priority but incomplete on real-world exploitation. CVSS 3.1 is 9.8 with AV:N/AC:L/PR:N/UI:N - network reachable, low complexity, no privileges, no user interaction, with High confidentiality, integrity, and availability impact - the most severe possible base profile for a scope-unchanged flaw. The CWE-347 root cause and 'JWT Attack'/'Authentication Bypass' tags corroborate a reliable, deterministic exploit primitive rather than a memory-corruption race, which typically means high automatability if a working technique is developed. However, EPSS is not provided, there is no POC referenced, and KEV status is negative, so exploitation probability cannot be quantified from the input. No SSVC decision data was supplied. Net: treat as a critical severity issue on paper; because the affected component is a Microsoft-hosted cloud service, remediation is largely Microsoft's responsibility server-side, which lowers customer-side action burden but does not lower the intrinsic severity.

Exploit ScenarioDerived

A remote, unauthenticated attacker crafts a token with forged or manipulated claims (e.g., an admin role) and submits it to the Microsoft 365 Admin Center, which fails to properly verify its cryptographic signature and honors the forged identity/authorization. Given AV:N/AC:L/PR:N/UI:N, the attacker needs only network access to the portal and no valid credentials or victim interaction, yielding elevated tenant privileges. No public POC is referenced at time of analysis.

Monitor Track and reassess. Why: Vendor states no customer action required.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 07, 2026

Privilege elevation in Microsoft 365 Admin Center allows a remote, unauthenticated attacker to gain elevated permissions by exploiting improper verification of a cryptographic signature (CWE-347), consistent with the vendor-supplied 'Authentication Bypass' and 'JWT Attack' tags. The maximal 9.8 CVSS with a fully network-reachable, no-privilege, no-interaction vector makes this a critical bypass of the admin portal's trust boundary. No public exploit identified at time of analysis, and it is not currently listed in CISA KEV.

RemediationAI

Because Microsoft 365 Admin Center is a Microsoft-operated cloud service, the fix is deployed server-side by Microsoft and generally requires no customer installation - Patch available per vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62873; confirm remediation status and any tenant-side action directly in that advisory. No exact fix version applies to a SaaS component. As compensating and detective controls, review Microsoft 365 admin audit logs and Entra ID sign-in/role-assignment logs for unexpected privilege escalations or anomalous administrative actions, enforce Conditional Access and phishing-resistant MFA on all admin roles, apply least-privilege and Privileged Identity Management (PIM) just-in-time role activation to shrink the blast radius of any forged-token access, and restrict admin portal access to managed devices or trusted network locations where feasible - noting that network/device restrictions can impede legitimate remote administration and should be validated against operational needs.

Affected VersionsENISA

Microsoft 365 Admin Center - (version not specified)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Microsoft 365 Admin Center is Microsoft's cloud-hosted administrative portal for managing M365 tenants (users, licenses, roles, security settings). CWE-347 (Improper Verification of Cryptographic Signature) is the root-cause class: the service accepts a token or message without correctly validating its signature. The 'JWT Attack' tag strongly implies the flaw lies in JSON Web Token validation - for example accepting an unsigned/alg:none token, failing to verify the signing key, or confusing symmetric and asymmetric key handling - which would let an attacker forge or tamper with an identity/authorization token. Because signature verification is the mechanism that binds a token's claims to a trusted issuer, its failure directly translates into an authentication/authorization bypass. No CPE strings were supplied since this is a Microsoft-operated SaaS service rather than customer-installed software.

Know when Jwt Attack gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 9.8 CRITICAL

Network-reachable signature-verification/JWT bypass needs no privileges or interaction (PR:N/UI:N/AC:L), and forged admin access yields high C/I/A over the tenant.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Improper verification of cryptographic signature in Microsoft 365 Admin Center allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

A critical authentication bypass in Microsoft 365 Admin Center enables unauthenticated attackers to remotely escalate to administrator privileges, potentially compromising entire Microsoft 365 tenants and sensitive organizational data. This vulnerability poses an immediate risk to any organization operating Microsoft 365 and requires urgent containment before a vendor patch becomes available. Without rapid mitigation, attackers could gain persistent admin access to email, collaboration platforms, and corporate data.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict Admin Center access to hardened, isolated administrative hosts with separate credentials; (2) Implement IP-based and geofence-based access controls; (3) Enable continuous monitoring and anomaly detection on administrative accounts; (4) Enforce advanced threat protection and real-time alerts for Admin Center activity; (5) Maintain detailed audit logs with extended retention for forensic investigation; (6) Disable non-critical administrative functions until patch availability; (7) Consider enhanced identity verification for any Admin Center access attempts.

Threat Intelligence Overview

EPSS Score
0.4%
Top 72% exploitable
Prevalence
High
core cloud admin portal for the vast M365 enterprise install base
Threat Intel
2
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:N/A
Service Type
Hosted
Vendor-managed, no client patch needed
Social Media
2
Sightings
Data Quality
8 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

54
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2013-3900 MEDIUM
5.5 Dec 11

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update

CVE-2026-48558 CRITICAL POC
9.5 Jun 12

Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke

CVE-2026-5430 CRITICAL POC
10.0 Aug 06

Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,

CVE-2025-59718 CRITICAL
9.8 Dec 09

Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to

CVE-2025-25291 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2026-47304 CRITICAL POC
9.8 Jul 14

Security feature bypass in Microsoft .NET (shipped via Visual Studio 2022 17.12/17.14 and Visual Studio 2026 18.7) lets

CVE-2025-25292 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2022-25898 CRITICAL POC
9.8 Jul 01

The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT

CVE-2026-107722 CRITICAL POC
9.8 Oct 08

Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a

CVE-2024-42004 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti

CVE-2024-41145 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27

CVE-2024-41138 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy