Azure Event Grid
CVE-2025-59273
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Event Grid network endpoint
-
DeliverySend request bypassing access-control check
-
ExploitExploit improper authorization (CWE-284)
-
ExecutionElevate privileges in service
-
ImpactAccess or alter protected resources/events
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The vulnerability resides in the Microsoft-managed Azure Event Grid service; per CVSS PR:N/UI:N/AC:L, exploitation is described as network-reachable by an unauthorized attacker with no authentication or user interaction and low complexity against the service's access-control logic. The primary limiting factor is the deployment model: Event Grid is a cloud PaaS offering, so remediation is applied centrally by Microsoft rather than by customers, substantially narrowing the real-world window of exposure. The description does not name a specific feature flag or non-default configuration as a prerequisite; however, because the flaw is a privilege-elevation issue ('elevate privileges'), the exact starting trust level required is ambiguous in the available data and should be verified via the MSRC advisory. |
| Impact | Signals are sharply conflicting. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N with C:H/I:H/A:H) paints a worst-case picture: network-reachable, low-complexity, no privileges or user interaction, full confidentiality/integrity/availability impact. However, the EPSS score is only 0.38% (30th percentile), indicating low modeled probability of exploitation in the near term, and there is no CISA KEV listing and no public exploit identified at time of analysis - so there is no evidence of active exploitation or weaponization. A critical mitigating factor the raw score ignores: Azure Event Grid is a Microsoft-operated cloud (PaaS) service, so the fix is deployed server-side by Microsoft and customers do not self-patch; the exposure window for most tenants is therefore controlled by Microsoft's remediation rather than customer action. Net assessment: this is a genuinely high-severity access-control/privilege-elevation flaw worth tracking, but the combination of low EPSS, no KEV, no POC, and vendor-managed remediation means it is not currently an active-exploitation emergency. The description ('improper access control ... elevate privileges') is terse and does not specify the exact trust boundary crossed; the PR:N (unauthenticated) rating should be verified against Microsoft's MSRC advisory, as privilege-elevation flaws sometimes require some pre-existing authenticated foothold. |
| Exploit ScenarioDerived | A remote attacker sends crafted requests to the Azure Event Grid service exploiting an improper access-control check, bypassing authorization boundaries to gain privileges they should not hold over resources or event data belonging to other principals. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) this requires only network access with low complexity and no authentication or user interaction. No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Azure Event Grid, Microsoft's fully managed event-routing service, can be abused by unauthenticated remote attackers to elevate privileges with high impact across confidentiality, integrity, and availability, per the CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - no credentials or user interaction are required and attack complexity is low. The root cause is improper access control (CWE-284) in the service's own authorization logic; because Event Grid is a multi-tenant cloud PaaS, any fix is applied centrally by Microsoft rather than by customers, which substantially narrows the real-world exposure window. No public exploit code has been identified at time of analysis and the EPSS score is low at 0.38% (30th percentile), so the 9.8 base score overstates near-term exploitation likelihood; an independent assessment confirms the primary limiting factor is the cloud-managed deployment model, and the exact starting trust level implied by 'elevate privileges' remains ambiguous in the available data.
RemediationAI
Remediation is not customer-applied: Microsoft owns the Event Grid control and data plane, so the fix for CVE-2025-59273 is deployed centrally by the service and customers should track confirmation of service-side remediation via the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59273; no customer-installable patch version is identified in the available data, and the MSRC entry is the authoritative source for status. In the meantime, treat any Event Grid credentials as potentially exposed and rotate shared access keys/SAS tokens used for publishing and subscribing, along with client secrets and certificates bound to those resources - the trade-off is a brief publishing outage for clients still using the old key, so stagger rotation or use two-key rollover. Audit all Event Grid resources (topics, domains, system topics, partner topics, namespaces, and event subscriptions) for unexpected subscriptions, unfamiliar publisher identities, or role assignments outside least privilege, and replace shared-key authentication with managed identities plus narrowly scoped EventGrid Data Sender/Contributor RBAC assignments, which removes static secrets but requires Entra ID configuration on each publisher. Where external publishers do not need public reachability, disable public network access or apply IP firewall rules and Private Endpoints - this reduces the network-exposed attack surface but will break any legitimate internet-based publisher. Finally, enable diagnostic and activity logs (and Microsoft Defender for Cloud alerts) for Event Grid resources to detect anomalous authorization or subscription changes, accepting the associated Log Analytics ingestion cost.
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
Azure Event Grid is a serverless, fully managed publish-subscribe and event-routing platform (topics, domains, system topics, partner topics, namespaces, and event subscriptions) that accepts events from Azure services and custom publishers and delivers them to subscribers via push or pull. Publishers and consumers normally authenticate with Microsoft Entra ID (Azure AD) identities, managed identities, or shared access signature (SAS) keys/access keys, and authorization is enforced through Azure RBAC role assignments and the service's internal access-control checks. CVE-2025-59273 is classified as CWE-284 (Improper Access Control), meaning the flaw is a logic-level authorization failure rather than a memory-safety or injection bug: the service evaluates a caller's identity, scope, or resource ownership incorrectly, permitting an unauthorized party to perform operations or assume a higher-privileged context than it should. Because the vulnerable component is Microsoft-operated control/data plane rather than customer-deployed software, the CPE record cpe:2.3:a:microsoft:azure_event_grid:-:*:*:*:*:*:*:* carries no version component - Event Grid is an evergreen, versionless cloud service, so per-tenant or per-region build states are not observable to customers. The CVSS vector's PR:N/UI:N indicates the advisory describes the access-control bypass as reachable over the network without prior authentication, which in a multi-tenant PaaS raises cross-tenant or cross-subscription authorization concerns; note that the independent assessment flags the precise prerequisite trust level as unconfirmed and recommends verification against the MSRC advisory.
Know when Azure Event Grid 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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-facing cloud service with improper access control permitting unauthenticated privilege elevation (AV:N/AC:L/PR:N/UI:N); full C/I/A impact consistent with EoP, scope unchanged within the service.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
Improper access control in Azure Event Grid allows an unauthorized attacker to elevate privileges over a network.
Executive ViewAI
A critical access control vulnerability in Microsoft Azure Event Grid (CVE-2025-59273) could allow unauthenticated remote attackers to elevate privileges and compromise confidentiality, integrity, and availability of event-driven workloads. Because Event Grid is a multi-tenant cloud service, Microsoft is responsible for applying any fix centrally, so customer exposure is tied to Microsoft's remediation timeline. Leadership should care because affected tenants may face data integrity, service disruption, or unauthorized access risks if the flaw is exploited, though no public exploit identified at time of analysis and EPSS is low.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to Azure Event Grid endpoints, enforcing least privilege and managed identities, enabling diagnostic logging and monitoring for anomalous authorization or event-routing activity, and engaging Microsoft support for centralized remediation guidance.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB