Skip to main content

Azure Compute Gallery CVE-2025-59503

CRITICAL
Server-Side Request Forgery (SSRF) (CWE-918)
2025-10-23 secure@microsoft.com
9.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Reach Azure Compute Gallery endpoint over network
  2. Delivery
    Send crafted request triggering SSRF
  3. Exploit
    Backend forwards request to internal Azure service
  4. Execution
    Access privileged internal APIs/metadata
  5. Impact
    Elevate privileges across network boundary

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

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

Exploitation Conditions

Exploitation targets Microsoft's cloud-hosted Azure Compute Gallery via the Azure Compute Resource Provider; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) it is remote and unauthenticated with low complexity and no user interaction, abusing SSRF to coerce the service into making attacker-influenced requests to internal/privileged endpoints to elevate privileges. The description specifies no feature toggle or non-default configuration prerequisite. The primary limiting factor is that this is a Microsoft-operated multi-tenant service: the vulnerability is remediated centrally by Microsoft (no customer patch deployment), which sharply narrows the realistic exploitation window; the terse advisory does not confirm whether specific gallery resource interaction or API access scoping further constrains the attack.

Impact

The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) frames this as a maximally severe network-exploitable flaw requiring no privileges or user interaction. However, the signals diverge sharply when cross-referenced: EPSS is only 0.77% (54th percentile), there is no CISA KEV listing, and no public exploit code was identified, so the real-world near-term exploitation likelihood is modest rather than imminent. Exploitation status is therefore 'no public exploit identified at time of analysis,' which should temper the raw 9.8. Critically, the affected component - Azure Compute Resource Provider / Azure Compute Gallery - is a Microsoft-operated cloud-side service, so remediation is performed centrally by Microsoft and typically requires no customer action; this materially reduces practical customer exposure compared to on-premises software carrying the same score. One conflict to flag: the description says an 'unauthorized attacker' can 'elevate privileges,' which is semantically awkward against PR:N (an already-unauthenticated attacker gaining elevated rights via SSRF against internal Azure endpoints) and also suggests a possible security-boundary crossing that Microsoft scored as S:U - verify scope and the exact privilege model with the MSRC advisory. No SSVC decision data was provided. Net: a genuinely high-severity SSRF, but given server-side remediation, low EPSS, and absence of KEV/POC, this reads as a serious-but-not-emergency issue for most tenants rather than an actively weaponized priority.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends crafted requests to the Azure Compute Gallery / Compute Resource Provider service, abusing a server-side request forgery flaw to make the backend issue requests to internal Azure endpoints it should not reach. By pivoting through the trusted service to internal metadata or privileged APIs, the attacker elevates privileges over the network. No public proof-of-concept was identified, and the vulnerability is a cloud-side service defect addressed by Microsoft centrally.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.8% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 08, 2026

Server-side request forgery in Microsoft's cloud-hosted Azure Compute Gallery allows unauthenticated remote attackers to coerce the Azure Compute Resource Provider into issuing attacker-influenced requests, ultimately elevating privileges within the service. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8), exploitation is network-reachable, low complexity, requires no authentication and no user interaction, and yields high confidentiality and integrity impact; the scope is unchanged. There is confirmed no public exploit code and no CISA KEV listing at time of analysis - no public exploit identified at time of analysis - and the EPSS score is modest at 0.77% (54th percentile), reflecting that the primary constraint is operational: the target is a Microsoft-operated multi-tenant service remediated centrally by Microsoft, not by customer patch deployment.

RemediationAI

Because Azure Compute Gallery is a Microsoft-operated multi-tenant service, remediation is applied server-side by Microsoft and customers cannot patch an installed binary; the authoritative guidance is the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59503, and per the available data no customer-deployable vendor patch version is identified - no vendor-released patch identified at time of analysis. Until Microsoft confirms service-side remediation, compensate by tightening the blast radius of the SSRF's privilege-elevation path: review and minimize role assignments on Gallery and Compute Resource Provider resources, removing Owner/Contributor and any custom roles with write or role-assignment permissions from principals that do not require them (trade-off: legitimate automation and pipeline service principals may need re-scoping or will break); restrict gallery sharing to explicitly trusted subscriptions and disable community or public gallery sharing where the feature is not needed (trade-off: loss of cross-tenant image distribution); and, where supported, apply Azure Policy and network controls to deny Gallery-related control-plane operations from untrusted source networks (trade-off: administrative lockout risk if allow-lists are incomplete). Detect abuse by monitoring Azure Activity logs for anomalous or unexpected Compute Gallery and Compute Resource Provider write operations and role-assignment changes from unusual principals or geolocations, and correlate with outbound requests attributed to the provider. No public exploit code exists at time of analysis, so these controls should be treated as precautionary hardening rather than emergency mitigations.

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

This is a CWE-918 server-side request forgery (SSRF) flaw in Azure Compute Gallery, the image-sharing and versioning service fronted by the Azure Compute Resource Provider (CPE cpe:2.3:a:microsoft:azure_compute_resource_provider:-:*:*:*:*:*:*:*, a version-agnostic CPE consistent with a cloud service rather than a downloadable package). In an SSRF, the vulnerable component accepts attacker-supplied input that influences the destination of a server-side HTTP request, so the provider - which sits inside Microsoft's trusted cloud network and typically holds managed identities and control-plane privileges - can be induced to reach internal or privileged endpoints that the external attacker cannot address directly. That trust-boundary crossing is what converts a request-manipulation bug into a high-impact integrity and confidentiality compromise, and it is why the assessed vector scores the confidentiality, integrity, and availability impacts as High while scope remains Unchanged. The terse MSRC advisory does not disclose the specific code path, parameter, or whether particular gallery resource operations or API scoping are prerequisites, so the precise request primitive that triggers the forgery is not independently confirmed from available data.

Know when Azure Compute Resource Provider 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

NVD PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Description supports remote unauthenticated SSRF with no interaction (AV:N/AC:L/PR:N/UI:N) yielding full privilege elevation (C/I/A:H); SSRF crossing internal boundaries could arguably warrant S:C, but S:U is retained to match the vendor rating.

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 NVD.

CVSS VectorNVD

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

DescriptionNVD

Server-side request forgery (ssrf) in Azure Compute Gallery allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

Microsoft's Azure Compute Gallery, a managed multi-tenant service, is affected by a critical server-side request forgery vulnerability (CVE-2025-59503) that could allow an unauthenticated attacker to escalate privileges within the service and potentially expose or alter cloud-hosted resources and data. Because this is a Microsoft-operated service, remediation is centralized by Microsoft rather than through customer patching, so the primary organizational exposure is to Azure workloads and data governed through the platform. Leadership should care if the organization relies on Azure Compute Gallery or Azure compute resources, as successful exploitation could undermine the confidentiality and integrity of cloud workloads; however, no public exploit identified at time of analysis and no CISA KEV listing is present.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include monitoring Microsoft security advisories and Microsoft Defender for Cloud, restricting Azure RBAC permissions for Azure Compute Gallery, enabling detailed logging and alerting on Azure Compute Resource Provider activity, limiting network egress from Azure workloads to required endpoints, and engaging Microsoft support for central remediation.

Threat Intelligence Overview

EPSS Score
0.8%
Top 46% exploitable
Prevalence
High
core Azure compute cloud service used by many enterprise tenants
Data Quality
3 sources
Confidence: Low

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.8%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

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

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

Affected Products (CPE)NVD

cpe:2.3:a:microsoft:azure_compute_resource_provider:-:*:*:*:*:*:*:*

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