CVE-2026-21531 — azure-ai-language-convers…
CRITICALCVE-2026-21531 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in azure-ai-language-conversations-authoring. A fix is available for azure-ai-language-conversations-authoring — see the affected versions and patch details below.
Azure AI Language Authoring Elevation of Privilege Vulnerability can Lead to RCE
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-21531.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
azure-ai-language-conversations-authoringReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Deserialization of untrusted data in the Azure AI Language Conversations Authoring client library for Python allows an unauthorized attacker to execute code over a network.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | azure-ai-language-conversations-authoring | all versions | 1.0.0b4pip install --upgrade 'azure-ai-language-conversations-authoring==1.0.0b4' |
Affected Products
azure conversation authoring client librarymicrosoftDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for azure-ai-language-conversations-authoring, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update azure-ai-language-conversations-authoring to 1.0.0b4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-21531 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2026-21531 in your dependencies?
Find it across PyPI, including transitive dependencies.