CVE-2025-66390

Cross‑Tenant Signup Bypass via Host Header Manipulation in Azure API Management

Published Jul 21, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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).

Analysis

AI-generated

Technical impact

The vulnerability allows an attacker to configure the Host header to reference a different tenant and then reuse the self‑service signup flow, even when that tenant has disabled the signup UI. This results in unintended account creation and access within the target tenant without proper authorization because the underlying API endpoint continues to accept cross‑tenant requests based solely on the Host header. The weakness is an improper access control flaw as identified by CWE‑284. The supplier evaluated this report and determined that it does not cross a security boundary, indicating that the observed behavior is a configuration/state issue rather than an exploitable product vulnerability affecting tenant isolation. This can lead to unauthorized user registration, privilege escalation within the target tenant, and a breach of tenant isolation without any additional exploits such as injection or buffer overflow.

Affected Systems

Microsoft Azure API Management is impacted when the self‑service signup option is enabled. The flaw exists in all releases up to and including 2025‑10‑17 that expose the signup API endpoint; there are no specific patch versions listed in the data, but the flaw applies to any configuration that does not fully disable the endpoint at the API level.

Risk and Exploitability

The flaw carries a CVSS of 9.8, indicating a critical severity. The EPSS score of <1% suggests that, in practice, exploitation attempts are currently rare, however the potential impact remains substantial. The vulnerability is not listed in the CISA KEV catalog. An attacker who controls the Host header or can forge cross‑tenant requests would be able to register a new account on a protected tenant, violating confidentiality and integrity of tenant isolation. The attack is likely straightforward and does not require complex prerequisites beyond accessing the signup API; the primary attack vector is the web API traffic where the Host header is manipulated.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Azure API Management service to a version released after 2025‑10‑17 that addresses the cross‑tenant signup handling.
  • Re‑configure tenant settings so that the self‑service signup option is disabled for all tenants and ensure that the underlying API endpoint is protected by host‑header validation that allows only the current tenant’s domain. This reduces the attack surface by preventing the API from accepting requests for unrelated tenants.
  • As a temporary measure, employ Azure Firewall or a network security group rule to block or rate‑limit requests to the signup endpoint that originate from external or unknown hosts, and explicitly validate the Host header on the API gateway level.

Generated by OpenCVE AI on August 4, 2026 at 05:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
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

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

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
Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Jul 22, 2026, 3:47 PM
Reserved
Nov 28, 2025, 12:00 AM
Status
Awaiting Analysis
Published
Jul 21, 2026, 2:16 PM
Modified
Oct 12, 2026, 7:10 PM