Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66390: n/a

0
Medium
VulnerabilityCVE-2025-66390cvecve-2025-66390
Published: 07/21/2026 (07/21/2026, 00:00:00 UTC)
Source: CVE Database V5

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).

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/21/2026, 14:12:22 UTC

Technical Analysis

The vulnerability in Microsoft Azure API Management allows an attacker to reuse the self-service signup registration flow from one tenant to another by modifying the hostname or tenant identifier. Although Tenant B has signup disabled at the UI level, the API endpoint still processes signup requests if the Host header is changed. The vendor evaluated this behavior and concluded it is a configuration or state management issue rather than a product vulnerability that breaks tenant isolation or security boundaries.

Potential Impact

The impact is limited to a configuration/state issue where signup disabling at the UI level does not prevent signup via the API endpoint when the Host header is manipulated. There is no breach of tenant isolation or security boundary according to the vendor. No known exploits are reported in the wild.

Mitigation Recommendations

As this is a cloud service, the vendor manages remediation. A patch is available according to the input data. Users should verify with the vendor advisory for current remediation status and apply any official fixes or updates provided by Microsoft Azure API Management to address this issue.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-28T00:00:00.000Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null
Is Cloud Service
true

Threat ID: 6a5f7ac92a4a8d598939c03e

Added to database: 07/21/2026, 13:57:29 UTC

Last enriched: 07/21/2026, 14:12:22 UTC

Last updated: 07/21/2026, 22:51:53 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses