Skip to main content
CVE-2025-59503VulnerabilityPublished Updated

CVE-2025-59503: Microsoft Azure Compute Resource Provider · Server-Side Request Forgery (SSRF)

Affects Microsoft Azure Compute Resource ProviderSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

Until an official patch is released by Microsoft, organizations should implement several specific mitigations: 1) Restrict network access to the Azure Compute Resource Provider endpoints using network security groups (NSGs) and firewall rules to limit exposure to trusted IP ranges only. 2) Employ strict egress and ingress filtering to prevent unauthorized internal requests that could be leveraged by SSRF. 3) Monitor Azure activity logs and network traffic for unusual or unexpected request patterns indicative of SSRF attempts. 4) Use Azure Policy to enforce least privilege and restrict permissions related to Compute Resource Provider operations. 5) Isolate sensitive workloads and management interfaces in separate virtual networks or subnets with limited connectivity. 6) Prepare for rapid patch deployment by establishing a vulnerability response plan and testing patch application procedures in advance. 7) Educate cloud administrators about SSRF risks and encourage vigilance for suspicious activity. These targeted actions go beyond generic advice by focusing on network-level controls and operational readiness specific to Azure environments.

Description

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

References

Community reviews

Loading reviews…