What is the CVSS score of CVE-2025-21415?

CVE-2025-21415 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 3.7%.

Which versions of Azure Ai Face Service are affected by CVE-2025-21415?

Organizations using Authentication bypass by spoofing in Azure AI Face Service face critical risk from CVE-2025-21415 rated CVSS 9.9.

How to fix or mitigate CVE-2025-21415?

Within 7 days: Identify all affected systems and apply vendor patches promptly. Monitor vendor channels for patch availability.

Azure Ai Face Service CVE-2025-21415

CRITICAL

Authentication Bypass by Spoofing (CWE-290)

2025-01-29 secure@microsoft.com

Microsoft Authentication Bypass Azure Ai Face Service

9.9

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:06 vuln.today

CVE Published

Jan 29, 2025 - 23:15 nvd

CRITICAL 9.9

DescriptionCVE.org

Authentication bypass by spoofing in Azure AI Face Service allows an authorized attacker to elevate privileges over a network.

AnalysisAI

Authentication bypass by spoofing in Azure AI Face Service allows an authorized attacker to elevate privileges over a network. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-290. Authentication bypass by spoofing in Azure AI Face Service allows an authorized attacker to elevate privileges over a network. Affected products include: Microsoft Azure Ai Face Service.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.