Skip to content- Sources: primary
- Summary: A post dated 2026-10-02 reports five elevation-of-privilege bugs in Azure API Connections, each reaching API Connections held by other tenants. The common cause is that the Azure API Management instance holds rights to every API Connection regardless of which one a request names, so path traversal through DynamicInvoke, undocumented sibling endpoints such as DynamicList, or the host.api.RuntimeUrl parameter was enough. The post states that Microsoft fixed each report with input validation or endpoint blocking rather than changing the token exchange, and that one fix validated the runtime URL before path normalization and so did not hold.
- Why it matters: Fixes applied at the request surface rather than at the token exchange leave the same design fact available to the next variant.
- Follow-up: Watch for a further variant or for a change to how API Management obtains API Connection tokens.