CVE-2025-53767VulnerabilityPublished 7 Aug 2025Updated 26 Feb 2026

CVE-2025-53767: Microsoft Azure Open AI · Server-Side Request Forgery (SSRF)

Affects Microsoft Azure Open AISource CVE Database V5

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: 1.1% chance of exploitation in 30 days – higher than 65% 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:N/E:U/RL:O/RC:C

Base metrics

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

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Until an official patch is released by Microsoft, organizations should implement several specific mitigations to reduce risk from CVE-2025-53767: 1) Restrict outbound network requests from Azure Open AI environments using network security groups (NSGs) or firewall rules to limit access to only trusted external endpoints and block internal metadata or management endpoints. 2) Monitor and log all outbound requests from Azure Open AI instances to detect anomalous or unexpected SSRF attempts. 3) Employ Azure Private Link or service endpoints to isolate Azure Open AI traffic from public internet exposure. 4) Use Azure Defender and other cloud security posture management tools to detect suspicious activities related to SSRF exploitation. 5) Review and harden application logic that interacts with Azure Open AI APIs to validate and sanitize all user-supplied URLs or request parameters. 6) Prepare incident response plans specifically addressing SSRF attack scenarios in cloud AI environments. 7) Stay updated with Microsoft security advisories and apply patches immediately upon release. These targeted actions go beyond generic advice by focusing on network-level controls, monitoring, and application-layer validation specific to Azure Open AI SSRF risks.

Description

Azure OpenAI Elevation of Privilege Vulnerability

Impact

The impact of CVE-2025-53767 is severe for organizations using Microsoft Azure Open AI services globally. Successful exploitation can lead to unauthorized access to internal Azure resources, sensitive customer data, and potentially allow attackers to escalate privileges within the cloud environment. This compromises confidentiality and integrity, undermining trust in cloud AI services and potentially causing significant data breaches or service disruptions. Organizations relying on Azure Open AI for critical AI workloads, data processing, or intellectual property risk exposure to espionage, data theft, and operational sabotage. The vulnerability's network-level exploitability without authentication or user interaction increases the attack surface and likelihood of automated exploitation attempts once public exploits emerge. The lack of current patches means organizations must rely on interim mitigations, increasing operational complexity and risk. Overall, this vulnerability threatens cloud security, customer data privacy, and the integrity of AI-driven applications and services worldwide.

Summary

CVE-2025-53767 is a critical Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918 affecting Microsoft Azure Open AI services. SSRF vulnerabilities occur when an attacker can manipulate a server to send crafted requests to unintended internal or external resources. In this case, the vulnerability allows unauthenticated remote attackers to exploit Azure Open AI's request handling mechanisms to perform SSRF attacks without any user interaction or privileges. The CVSS v3.1 base score of 10.0 reflects the vulnerability's ease of exploitation (attack vector: network, attack complexity: low), lack of required privileges or user interaction, and its impact on confidentiality and integrity with a scope change. Exploiting this flaw could enable attackers to access internal Azure infrastructure or customer data, escalate privileges, and potentially pivot to further attacks within the cloud environment. Although no public exploits are currently known, the critical nature of the vulnerability and the widespread use of Azure Open AI services make it a high-risk issue. The vulnerability was reserved in early July 2025 and published in August 2025, with no patches yet available, emphasizing the need for immediate defensive measures. The absence of patch links suggests that mitigation currently relies on configuration and network controls. This vulnerability highlights the risks associated with SSRF in cloud-hosted AI services, where internal APIs and metadata services may be exposed indirectly through vulnerable request handling.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53767 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 03:24 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats