Azure Ai Foundry
Monthly
Server-side request forgery in Azure AI Foundry can be exercised by an authenticated user with low privileges over the network, allowing the service to be induced to make requests that may expose sensitive information and cross a scope boundary. The affected product is Microsoft's Azure AI Foundry cloud service; no public exploit was identified at the time of analysis and no KEV designation is present in the supplied data, while Microsoft has published a vendor fix. This is a genuine but moderate-priority issue rather than a drop-everything emergency, and the exact feature, API, or request parameter that triggers the server-side request is not described in the available sources.
Server-side request forgery in Azure AI Foundry allows remote unauthenticated attackers to cause high confidentiality loss by making the service fetch attacker-controlled URLs. Microsoft applies the fix server-side, requiring no customer action, and no public exploit has been identified at time of analysis.
Unauthenticated remote attackers can reach a critical function inside Microsoft Azure AI Foundry that performs a privileged operation without any authentication check, giving high confidentiality, integrity and availability impact across the affected service (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, CWE-306). The weakness lives in a Microsoft-operated cloud service rather than a customer-installable product, so both the exposed surface and the fix are controlled server-side by Microsoft and the specific impacted feature is not publicly disclosed. Exploitation signals currently conflict: no public exploit code has been identified and CISA's SSVC rates exploitation as 'none' (automatable: yes, technical impact: total) with a low EPSS of 0.49% (41st percentile), yet the unauthenticated, no-user-interaction path makes the bug trivially automatable once technical details circulate.
Improper access control in Microsoft Azure AI Foundry agents published to Microsoft 365 lets unauthenticated remote attackers elevate privileges across a network boundary, and Microsoft rates the flaw CVSS 10.0 with scope change and high confidentiality, integrity, and availability impact. Only environments with agents published to Microsoft 365 are in scope; the precise access-control defect and its trigger are not described in the available sources. Microsoft lists a vendor-side patch, EPSS is 0.04% (13th percentile), CISA SSVC reports no known exploitation, and no public exploit was identified at time of analysis, so the vuln.today decision label is monitor despite the maximum base score.
Azure AI Foundry improper authorization permits unauthenticated remote attackers to escalate privileges and achieve complete compromise with high impact to confidentiality, integrity, and availability. The CVSS 10.0 rating reflects network-based attack vector with low complexity, no user interaction, and scope change indicating containerization/isolation escape. EPSS and KEV status not provided, but the authentication bypass affecting a cloud AI platform poses severe risk. No public exploit identified at time of analysis.
Server-side request forgery in Azure AI Foundry can be exercised by an authenticated user with low privileges over the network, allowing the service to be induced to make requests that may expose sensitive information and cross a scope boundary. The affected product is Microsoft's Azure AI Foundry cloud service; no public exploit was identified at the time of analysis and no KEV designation is present in the supplied data, while Microsoft has published a vendor fix. This is a genuine but moderate-priority issue rather than a drop-everything emergency, and the exact feature, API, or request parameter that triggers the server-side request is not described in the available sources.
Server-side request forgery in Azure AI Foundry allows remote unauthenticated attackers to cause high confidentiality loss by making the service fetch attacker-controlled URLs. Microsoft applies the fix server-side, requiring no customer action, and no public exploit has been identified at time of analysis.
Unauthenticated remote attackers can reach a critical function inside Microsoft Azure AI Foundry that performs a privileged operation without any authentication check, giving high confidentiality, integrity and availability impact across the affected service (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, CWE-306). The weakness lives in a Microsoft-operated cloud service rather than a customer-installable product, so both the exposed surface and the fix are controlled server-side by Microsoft and the specific impacted feature is not publicly disclosed. Exploitation signals currently conflict: no public exploit code has been identified and CISA's SSVC rates exploitation as 'none' (automatable: yes, technical impact: total) with a low EPSS of 0.49% (41st percentile), yet the unauthenticated, no-user-interaction path makes the bug trivially automatable once technical details circulate.
Improper access control in Microsoft Azure AI Foundry agents published to Microsoft 365 lets unauthenticated remote attackers elevate privileges across a network boundary, and Microsoft rates the flaw CVSS 10.0 with scope change and high confidentiality, integrity, and availability impact. Only environments with agents published to Microsoft 365 are in scope; the precise access-control defect and its trigger are not described in the available sources. Microsoft lists a vendor-side patch, EPSS is 0.04% (13th percentile), CISA SSVC reports no known exploitation, and no public exploit was identified at time of analysis, so the vuln.today decision label is monitor despite the maximum base score.
Azure AI Foundry improper authorization permits unauthenticated remote attackers to escalate privileges and achieve complete compromise with high impact to confidentiality, integrity, and availability. The CVSS 10.0 rating reflects network-based attack vector with low complexity, no user interaction, and scope change indicating containerization/isolation escape. EPSS and KEV status not provided, but the authentication bypass affecting a cloud AI platform poses severe risk. No public exploit identified at time of analysis.