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).
CVE-2025-66390
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 25, 2026GitHub - bountyyfi/Azure-APIM-Cross-Tenant-Signup-Bypass: Security advisory: Azure APIM Developer Portal allows cross-tenant account registration by bypassing UI signup restrictions. Reported to MSRC twice - closed as "by design". · GitHub
https://github.com/bountyyfi/Azure-APIM-Cross-Tenant-Signup-BypassAzure APIM Cross-Tenant Signup Bypass · Advisory · bountyyfi/Azure-APIM-Cross-Tenant-Signup-Bypass · GitHub
https://github.com/bountyyfi/Azure-APIM-Cross-Tenant-Signup-Bypass/security/advisories/GHSA-vcwf-73jp-r7mvVendor Advisories for CVE-2025-66390(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 43× in last 7d / 55× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 15:58 UTCGHSA enrichment
- 2026-07-30 11:58 UTCEG score recompute
- 2026-07-30 11:58 UTCGHSA enrichment
- 2026-07-30 08:01 UTCGHSA enrichment
- 2026-07-30 03:30 UTCEG score recompute
- 2026-07-30 03:30 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 23:44 UTCGHSA enrichment
- 2026-07-29 19:56 UTCGHSA enrichment
- 2026-07-29 15:36 UTCGHSA enrichment
- 2026-07-29 11:51 UTCGHSA enrichment
- 2026-07-29 08:05 UTCGHSA enrichment
- 2026-07-29 04:20 UTCGHSA enrichment
- 2026-07-29 00:34 UTCGHSA enrichment
- 2026-07-28 20:49 UTCGHSA enrichment
- 2026-07-28 17:03 UTCEG score recompute
- 2026-07-28 17:03 UTCGHSA enrichment
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-28 11:52 UTCGHSA enrichment
- 2026-07-28 08:04 UTCGHSA enrichment
- 2026-07-28 04:19 UTCGHSA enrichment
- 2026-07-28 00:34 UTCGHSA enrichment
- 2026-07-27 20:49 UTCGHSA enrichment
- 2026-07-27 17:00 UTCEG score recompute
- 2026-07-27 17:00 UTCGHSA enrichment
Show 30 moreShow fewer
- 2026-07-27 14:12 UTCEPSS rescore
- 2026-07-27 13:14 UTCGHSA enrichment
- 2026-07-27 09:29 UTCGHSA enrichment
- 2026-07-27 05:44 UTCGHSA enrichment
- 2026-07-27 01:58 UTCGHSA enrichment
- 2026-07-26 22:11 UTCGHSA enrichment
- 2026-07-26 18:26 UTCEG score recompute
- 2026-07-26 18:26 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:30 UTCGHSA enrichment
- 2026-07-26 10:44 UTCEG score recompute
- 2026-07-26 10:44 UTCGHSA enrichment
- 2026-07-26 04:25 UTCEG score recompute
- 2026-07-26 04:24 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:01 UTCEG score recompute
- 2026-07-22 23:25 UTCEG score recompute
- 2026-07-22 23:24 UTCGHSA enrichment
- 2026-07-22 16:03 UTCEG score recompute▲ 9.80
- 2026-07-22 16:03 UTCGHSA enrichment
- 2026-07-22 16:00 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 14:51 UTCNVD update
- 2026-07-21 14:00 UTCEG score recompute
- 2026-07-21 13:57 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2025-66390?
When was CVE-2025-66390 disclosed?
Is CVE-2025-66390 actively exploited?
What is the CVSS score of CVE-2025-66390?
How do I remediate CVE-2025-66390?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-66390
Is Your Infrastructure Affected by CVE-2025-66390?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.