Cross‑Tenant Signup Bypass via Host Header Manipulation in Azure API Management
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Microsoft | Azure Api Management |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.435% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑Tenant Signup Bypass via Host Header Manipulation in Azure API Management |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑Tenant Signup Bypass in Azure API Management via Host Header Manipulation |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft
Microsoft azure Api Management |
|
| Vendors & Products |
Microsoft
Microsoft azure Api Management |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑Tenant Signup Bypass in Azure API Management via Host Header Manipulation |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-284 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Microsoft Azure API Management through 2025-10-17, when self-service signup (username/password Basic Authentication) is enabled in Tenant A, an attacker can reuse the registration flow by changing the hostname or tenant identifier to Tenant B, even when Tenant B has signup disabled at the UI level. In other words, disabling signup in the UI does not disable the underlying API endpoint (which still accepts cross-tenant requests based on the Host header). NOTE: The supplier states that they evaluated the report and determined it did not cross a security boundary (i.e., the observed behavior was a configuration/state issue rather than an exploitable product vulnerability affecting tenant isolation). NOTE: The supplier evaluated this report and determined that it did not cross a security boundary (i.e., the observed behavior was a configuration/state issue rather than an exploitable product vulnerability affecting tenant isolation). | |
| References |
|