Skip to main content

Azure AI Language CVE-2026-70352

| EUVDEUVD-2026-70793 CRITICAL
Missing Authentication for Critical Function (CWE-306)
2026-09-03 secure@microsoft.com GHSA-jh5m-2prj-924w
10.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Reach exposed Azure AI Language endpoint
  2. Delivery
    Send request to unauthenticated critical function
  3. Exploit
    Bypass missing authentication
  4. Execution
    Invoke privileged operation
  5. Impact
    Elevate privileges across scope boundary

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires only network access to the affected Azure AI Language function; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) there is no authentication, no user interaction, and no special configuration required beyond the service being reachable. The chief limiting factor is that Azure AI Language is a Microsoft-hosted service, so once Microsoft deploys its server-side fix the vulnerable path is closed for all tenants regardless of customer action; customers who additionally place the resource behind private endpoints or IP firewalls further reduce who can reach the endpoint.

Impact

The signals are consistently severe: the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C with C:H/I:H/A:H yields the maximum 10.0, meaning remote, unauthenticated, low-complexity exploitation with high impact across a changed scope. No EPSS score, CISA KEV entry, or public POC is provided, so there is no evidence of active exploitation or widespread weaponization yet - the risk is driven by severity and reachability rather than observed attacks. As a Microsoft-operated cloud service, remediation is largely server-side and applied by the vendor, which greatly limits the window and customer action required compared to on-premises software; however, any operator relying on Azure AI Language should still confirm they are on Microsoft's fixed service build and review access. The primary uncertainty is that the MSRC advisory is the sole reference and the description is terse, so exploitation mechanics and any residual customer-side prerequisites are not independently verifiable.

Exploit ScenarioDerived

A remote attacker with no credentials sends crafted requests directly to the unauthenticated critical function of Azure AI Language over the network and, because identity is never verified, invokes privileged operations to elevate their access beyond the intended boundary. No public POC is indicated, but the low complexity and lack of authentication or user interaction make reliable exploitation straightforward for anyone who can reach the endpoint.

Monitor Track and reassess. Why: Vendor states no customer action required.
No patch listed yet 0.6% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 03, 2026

Privilege elevation in Microsoft's Azure AI Language cloud service lets a remote, unauthenticated attacker reach a critical function that lacks authentication (CWE-306), gaining elevated privileges over the network. Rated CVSS 10.0 with a scope change (S:C), the flaw is disclosed and fixed by Microsoft via MSRC; no public exploit code or CISA KEV listing is indicated, so this is no public exploit identified at time of analysis.

RemediationAI

Because Azure AI Language is a Microsoft-managed cloud service, the fix is deployed by Microsoft on the service side; patch available per vendor advisory (MSRC), with no customer-installable version specified in the input - consult https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70352 to confirm the service is remediated and whether any tenant-side action is required. As compensating controls pending or in addition to confirmation, restrict network reachability to your Azure AI Language resources using private endpoints/VNet integration and IP firewall rules so the service is not exposed to arbitrary internet callers, enforce authentication via Microsoft Entra ID (managed identities) instead of relying solely on keys, and rotate any resource access keys; the trade-off is that private endpoints and IP restrictions can break integrations that call the service from unlisted networks and require configuration on each consuming application. Review Azure activity and diagnostic logs for anomalous privilege changes or unexpected calls during the exposure window.

Affected VersionsENISA

Azure AI Language Authoring - (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

Azure AI Language is Microsoft's managed cloud natural-language-processing service (part of Azure AI/Cognitive Services) offering entity recognition, sentiment, summarization, and custom text classification via REST APIs. The root cause is CWE-306, Missing Authentication for Critical Function: a security-sensitive operation is exposed without verifying the caller's identity, so requests that should require an authenticated, authorized principal are honored from anyone who can reach the endpoint. Because the CVSS scope is Changed (S:C), the impacted authority boundary differs from the vulnerable component, consistent with a privilege-elevation effect that crosses into resources beyond the initially reachable component.

Know when Azure Ai Language Authoring 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 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 10.0 CRITICAL

Missing authentication on a network-reachable critical function gives PR:N/AV:N/AC:L; privilege elevation across the service boundary supports S:C with high C/I/A.

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

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
High
Availability
High

DescriptionCVE.org

Missing authentication for critical function in Azure AI Language allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

A critical authentication bypass in Microsoft Azure AI Language allows unauthenticated remote attackers to gain elevated privileges with potential impact to dependent systems and organizational data. No public exploit has been identified at time of analysis, but the CVSS 10.0 rating demands immediate patching per Microsoft MSRC advisory and security audit.

Business Impact: Severe
Compensating Controls

Apply vendor patch released by Microsoft via MSRC immediately. Interim mitigations if patching is delayed: restrict network access to Azure AI Language using Azure Network Security Groups and IP whitelisting; disable the service if not actively required; implement enhanced monitoring and alerting on API calls for anomalous activity.

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Prevalence
Medium
widely-used Azure cloud NLP service, but not universally deployed
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:N/A
Service Type
Hosted
Vendor-managed, no client patch needed
Social Media
2
Sightings
Data Quality
7 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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
Vendor states no customer action required
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
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
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