🛡️ CVE-2026-24303 — partner-center

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Changed — a successful attack reaches components beyond the vulnerable one.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: None.

Weakness class

CVE-2026-24303 is classified as CWE-284: Improper Access Control. The software does not restrict an action to the actors that should be allowed to perform it.

Affected software

CVE-2026-24303 is recorded against 1 package.

• partner-center

Timeline and source

Published on 23 April 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

msrc.microsoft.com

Other advisories for this package

partner-center has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2026-34327 (8.2 High, published 7 May 2026)
• CVE-2025-65041 (10.0 Critical, published 18 Dec 2025)
• CVE-2025-29814 (9.3 Critical, published 21 Mar 2025)
• CVE-2024-49035 (8.7 High, published 26 Nov 2024)

Same weakness in other software

These advisories are the same class of weakness (CWE-284: Improper Access Control) in other software:

• CVE-2022-29160 (2.0 Low, published 12 Jul 2026)
• CVE-2022-45438 (published 7 Jul 2026)
• CVE-2016-0757 (published 6 Jul 2026)
• CVE-2002-0170 (8.0 High, published 2 Jul 2026)
• CVE-2000-1212 (published 2 Jul 2026)
• CVE-2022-31231 (5.9 Medium, published 22 May 2026)
• CVE-2023-24215 (9.1 Critical, published 18 May 2026)
• CVE-2022-21619 (3.7 Low, published 8 May 2026)

Details

Affected Packages

References