Skip to main content

Azure Active Directory CVE-2026-45480

| EUVDEUVD-2026-38086 CRITICAL
Improper Authentication (CWE-287)
2026-06-19 secure@microsoft.com GHSA-rfvj-frr3-5qvh
10.0
CVSS 3.1 · Vendor: microsoft
Temporal: 8.7
View

Attack ChainAIDerived

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

  1. Access
    Identify target Azure AD tenant
  2. Delivery
    Send crafted request to auth endpoint
  3. Exploit
    Bypass identity verification
  4. Execution
    Obtain privileged token
  5. Persist
    Access federated resources cross-tenant
  6. Impact
    Exfiltrate data or persist via app registrations

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of Azure Active Directory, per CVSS AV:N/AC:L/PR:N/UI:N. The only practical limiter is network reachability to Azure AD authentication endpoints (login.microsoftonline.com and related), which is by design exposed to the public internet for every tenant, so essentially every Azure AD / Entra ID customer is in scope unless Microsoft has already deployed a server-side fix. The supplied description does not enumerate any product feature, configuration toggle, or deployment mode that must be enabled, and no platform-specific or client-version preconditions are indicated.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H represents the worst-case profile: network-reachable, no authentication, no user interaction, low complexity, and a scope change with full CIA impact - hence the 10.0 score. EPSS data was not provided, and the CVE is not listed in CISA KEV in the input, so there is no public exploit identified at time of analysis; however, an unauthenticated network-reachable auth bypass in a global identity provider is a top-tier target and high-value for threat actors. The Microsoft Security Response Center reporter (secure@microsoft.com) and the 'Authentication Bypass' tag corroborate the CVSS characterization. Key data is missing: no description of the specific attack precondition, no fix version, and no confirmation of patch deployment status - for a cloud service this is often handled server-side by Microsoft transparently, but customers cannot independently verify mitigation without further advisory detail.

Exploit ScenarioDerived

An unauthenticated attacker on the public internet crafts a request to an Azure AD authentication endpoint that bypasses identity verification, obtaining a token or session that asserts a privileged identity (for example, a Global Administrator) in a target tenant. Because the CVSS scope is Changed, the attacker then pivots from the identity plane to downstream Microsoft 365 mailboxes, SharePoint, Azure subscriptions, and any SaaS application federated to that tenant. No public exploit identified at time of analysis, but the AV:N/AC:L/PR:N/UI:N profile means exploitation would be straightforward once the technique is known.

Monitor Track and reassess. Why: Vendor states no customer action required.
Patch available 0.6% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jun 19, 2026

Privilege escalation in Microsoft Azure Active Directory allows unauthenticated remote attackers to bypass authentication controls and gain elevated access across tenant boundaries. With a maximum CVSS score of 10.0 and a scope-changing impact, successful exploitation could compromise identity, access, and resources federated through Azure AD. No public exploit identified at time of analysis, but the trivial attack complexity and network-reachable vector make this a top-priority issue for any organization relying on Azure AD for identity.

RemediationAI

Because Azure AD is a Microsoft-operated cloud service, the primary remediation path is server-side mitigation by Microsoft rather than a customer-installed patch; patch available per vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45480, which customers should review to confirm whether tenant action (e.g., rotating refresh tokens, revoking sessions, updating libraries like MSAL/ADAL, or reconfiguring federation) is required. As compensating controls while validating the fix, enforce Conditional Access policies that require compliant devices and trusted network locations, require phishing-resistant MFA (FIDO2/Windows Hello) for privileged roles, restrict legacy authentication protocols, and monitor sign-in logs for anomalous token issuance - note that aggressive conditional access can break legitimate B2B/guest workflows and service principal authentications, so test in report-only mode first. Consider revoking all refresh tokens for privileged accounts via Revoke-AzureADUserAllRefreshToken to force re-authentication once Microsoft confirms the issue is remediated.

Affected VersionsENISA

Azure Active Directory - (version not specified)

Affected Packages

microsoft azure_active_directory fix: Azure Active Directory

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in microsoft

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

Technical ContextAI · show details

Azure Active Directory (now branded Microsoft Entra ID) is Microsoft's cloud identity and access management service used to authenticate users and applications across Microsoft 365, Azure, and federated third-party SaaS. The root-cause class CWE-287 (Improper Authentication) means the service fails to correctly verify that a principal is who it claims to be - examples include token validation flaws, missing signature checks, replayable assertions, or logic errors that accept malformed credentials. Because Azure AD issues OAuth 2.0/OIDC tokens and SAML assertions consumed by downstream resources, an authentication flaw at the identity provider cascades into any application trusting those tokens. No specific CPE strings were provided in the input to narrow the affected component (sign-in service, token issuance, B2B/B2C, federation, etc.).

Know when Azure Active Directory 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 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CIRCL (temporal) 8.7 HIGH
vuln.today AI 10.0 CRITICAL

Unauthenticated network-reachable auth bypass in an identity provider yields PR:N/UI:N/AC:L; scope changes because compromised IdP impacts downstream relying parties with full CIA loss.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/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:H/SI:H/SA:H

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

DescriptionCVE.org

Improper authentication in Azure Active Directory allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

Microsoft Azure Active Directory is vulnerable to a critical authentication bypass (CVE-2026-45480, CVSS 10.0) that allows unauthenticated remote attackers to escalate privileges and cross tenant boundaries. This vulnerability compromises the foundational identity and access control mechanism relied upon across most enterprise cloud infrastructure, exposing all federated users and resources to unauthorized access. Immediate detection and remediation are required to prevent full-scale identity compromise.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: enforce mandatory MFA across all users, implement IP-based conditional access to restrict authentication to trusted networks, disable legacy authentication protocols, enable and monitor Azure AD sign-in risk detection and anomalous activity alerts, restrict cross-tenant access policies to explicitly approved partners only, and conduct continuous audits of privilege assignments and access grants.

Threat Intelligence Overview

EPSS Score
0.6%
Top 57% exploitable
Vendor Action
No Action
Not required. The vulnerability documented by this CVE requires no customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Service Type
Hosted
Vendor-managed, no client patch needed
Social Media
2
Sightings
Data Quality
7 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.6%
Patch available Yes
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

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

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

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