CVE-2025-66390
CriticalCVSS 9.8Exploitation Probability (EPSS)
Low risk27th percentile - higher than 27% of all known CVEs
Summary
In Microsoft Azure API Management, when self-service signup (Basic Authentication) is enabled, an attacker can reuse the registration flow for another tenant by changing the Host header, even if signup is disabled in the UI. The vendor considers this a configuration issue, not a vulnerability.
Risk Assessment
Risk of unauthorized account creation in another tenant, potentially leading to tenant isolation breach.
Recommendation
Review API endpoint configuration and consider disabling self-service signup or applying additional network-level protections.
Related vulnerabilities
- CVE-2026-86106Critical
An unauthenticated actor with network access to the private HA interconnect may trigger sensitive HA peer functions without verification. This could result in elevated command execution on Edge units where HA is enabled.
- CVE-2026-73453Critical
An unauthenticated P4Runtime client can achieve arbitrary code execution under certain conditions on affected platforms running Arista EOS configured with P4Runtime. By crafting a malicious packet during session initiation, an attacker can obtain complete administrative control over the switch.
- CVE-2026-81642Critical
In NLnet Labs Unbound up to and including 1.26.0, a vulnerability in the DNSSEC validator enables denial of service and possible remote code execution via DNSKEY processing. A crafted DNSKEY can overflow the digest buffer.
- CVE-2026-27565Critical
An unauthenticated remote attacker can upload a malicious IODD file that places and executes a shell script with root privileges. The script remains active even after a reboot.
- CVE-2026-27546Critical
An unauthenticated remote attacker can exploit an authentication bypass in the _account_log function to log in as an admin, even when accounts are properly configured.
- CVE-2026-73447Critical
A privileged attacker can exploit gNSI Certz service on Arista EOS-based products to escalate privileges and execute arbitrary OS commands via a crafted Certz Rotate request. The Bootz service is also affected.
- CVE-2026-14349Critical
The TrueBooker – Appointment Booking and Scheduler System plugin for WordPress in all versions up to and including 1.2.3 is vulnerable to authorization bypass. This is due to the plugin not properly verifying that a user is authorized to perform an action. This allows unauthenticated attackers to modify the email address of arbitrary user accounts, including administrators, which can be leveraged to reset the account password and gain access.
- CVE-2026-12793Critical
The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress in all versions up to and including 3.6.2 is vulnerable to Privilege Escalation. This is due to the plugin not validating that a submitted form ID belongs to a JetFormBuilder form before parsing the referenced post's content as form schema and executing an Advanced Validation server-side callback. This allows unauthenticated attackers to create a new administrator-level user account.
- CVE-2026-15640Critical
Under certain conditions a valid SAML IdP response may be used to impersonate another Secret Server user. The vulnerability affects the SAML authentication mechanism.
- CVE-2026-15639Critical
An attacker can craft a malicious link that, if used by a legitimate user, may cause the user's browser to run JavaScript supplied by the attacker. The vulnerability affects the link processing mechanism.
Original NVD description (English source)
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).

