Skip to main content

Microsoft Partner Center EUVDEUVD-2026-63628

| CVE-2026-69558 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-08-20 microsoft GHSA-7fcf-m943-h7cx
8.6
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify Partner Center API endpoints
  2. Delivery
    Manipulate tenant or resource identifier in request
  3. Exploit
    Submit request bypassing authorization checks
  4. Execution
    Receive cross-tenant confidential data in response
  5. Impact
    Exfiltrate partner or customer records at scale

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates network access is sufficient with no authentication barrier per the official scoring, and the underlying condition is the application's use of user-supplied keys or resource identifiers as the sole access control mechanism without server-side authorization validation (CWE-639). Exploitation is limited to confidentiality impact only - I:N and A:N confirm that data cannot be modified and service availability is not affected. A meaningful uncertainty exists: Partner Center is a portal that ordinarily requires a Microsoft partner account, and the PR:N rating conflicts with that access model; the exact authentication threshold (none vs. low-privilege account) must be confirmed from the MSRC advisory before concluding that zero-credential exploitation is achievable. Exploitation scope is bounded to data accessible through the Partner Center API surface.

Impact

The CVSS 3.1 score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) rates this as High severity with a fully network-accessible attack surface, low complexity, and no stated prerequisites, making the vulnerability attractive for automated enumeration at scale. The Scope:Changed and C:H combination indicates cross-tenant data disclosure - potentially customer records, subscription details, billing information, or organizational profiles - as the primary risk. No EPSS score was supplied and the CVE is not listed in the CISA KEV catalog at time of analysis, meaning widespread or opportunistic exploitation has not been confirmed; however, the sensitivity of partner ecosystem data and the zero-friction CVSS profile warrant urgent patch prioritization regardless of observed exploitation activity. A notable tension exists between the PR:N rating and the reality that Partner Center is a portal normally requiring a Microsoft partner account: whether exploitation is truly pre-authentication or requires a minimal account should be verified against the vendor advisory before concluding zero-credential exploitation is confirmed.

Exploit ScenarioDerived

An attacker with network access submits API requests to Microsoft Partner Center, substituting or incrementing resource or tenant identifiers within the request parameters to bypass authorization checks and retrieve confidential data belonging to other partner tenants - such as customer subscription details, billing records, or organizational profiles. The low attack complexity and absence of required privileges per the CVSS vector mean that exploitation can be scripted and executed at volume against the Partner Center API surface. No public proof-of-concept code has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 20, 2026

Microsoft Partner Center exposes cross-tenant information to unauthenticated network attackers via an authorization bypass rooted in user-controlled key manipulation (CWE-639). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H) indicates low-complexity, scopechanging exploitation that can reach confidential partner or customer data beyond the attacker's own organizational boundary. A vendor-released patch is available through the Microsoft Security Response Center; no public exploit has been identified at time of analysis.

RemediationAI

The primary fix is the vendor-released patch available through the Microsoft Security Response Center at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69558; the exact patched version number is not specified in currently available data and must be confirmed directly from the MSRC advisory. Organizations should monitor that advisory for patch version details and deploy the update promptly given the unauthenticated network attack vector. As a compensating control while awaiting patch deployment, administrators should review Partner Center audit logs for anomalous cross-tenant API access patterns and, where technically feasible, restrict Partner Center API access to known corporate IP ranges; note that IP allowlisting may disrupt legitimate remote partner access and is not universally supported across all Partner Center API surfaces. Disabling or throttling bulk resource-enumeration API calls at the network perimeter can reduce automated exploitation risk but will not eliminate the underlying authorization flaw.

Affected VersionsENISA

Microsoft Partner Center - (version not specified)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Microsoft Partner Center (CPE: cpe:2.3:a:microsoft:microsoft_partner_center:*:*:*:*:*:*:*:*) is a web-based portal used by Microsoft partners - managed service providers, independent software vendors, and distributors - to manage customer relationships, cloud subscriptions, licenses, and billing. The root cause is CWE-639, Authorization Bypass Through User-Controlled Key: the application relies on a caller-supplied identifier (such as a resource ID, tenant ID, or object key) as the primary access control mechanism without sufficient server-side validation. An attacker who can substitute or enumerate these keys retrieves data belonging to other tenants or users. The Scope:Changed metric in the CVSS vector confirms the impact crosses authorization boundaries, affecting resources outside the attacker's own organizational context - characteristic of an Insecure Direct Object Reference (IDOR) pattern at the API layer.

Know when Microsoft Partner Center gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 8.6 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
vuln.today AI 7.7 HIGH

Partner Center requires at minimum a partner account to interact with its API, making PR:L more accurate than PR:N; all other metrics align with the network-accessible, scope-changing, confidentiality-only disclosure pattern.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Authorization bypass through user-controlled key in Microsoft Partner Center allows an unauthorized attacker to disclose information over a network.

Executive ViewAI

Why It Matters

Microsoft Partner Center (CVE-2026-69558, CVSS 8.6) contains an authorization bypass allowing unauthenticated attackers to access confidential data across customer and partner tenants without credentials. This scope-changing vulnerability creates direct exposure of sensitive organizational relationships and customer data, affecting every organization using Partner Center for vendor or partner management. Remediation is urgent to prevent data breach and regulatory notification obligations.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 56% exploitable
Prevalence
Medium
widely used portal across global Microsoft partner ecosystem
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More Likely
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy