CVE-2026-21531: Microsoft Azure AI Language Authoring · Deserialization of Untrusted Data
Affects Microsoft Azure AI Language AuthoringSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.0.0b4 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 2.5% chance of exploitation in 30 days – higher than 85% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.0b4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade Microsoft Azure AI Language Authoring to 1.0.0b4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MicrosoftAzure AI Language Authoring | Affected
| Fixed in
|
AI-suggested
Microsoft has released an official fix for this vulnerability. As this is a cloud-hosted service, Microsoft manages the remediation server-side. Users should verify that their Azure AI Language Authoring service is updated according to the Microsoft advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21531. No additional user action is required beyond ensuring the service is current with the vendor's fix.
Description
Deserialization of untrusted data in Azure SDK allows an unauthorized attacker to execute code over a network.