Unauthenticated code execution via unsafe token deserialization
Published Feb 10, 2026 · Updated Feb 10, 2026
Deserialization in Microsoft Azure AI Language Conversations Authoring before 1.0.0b4 allows remote attackers to execute arbitrary code. The continuation-token restoration path deserializes a caller-supplied token as a Python object without authenticity or type validation. Exploitation requires an application to process an attacker-controlled continuation token; no authentication or user interaction is required.
Summary
What happened
Deserialization in Microsoft Azure AI Language Conversations Authoring before 1.0.0b4 allows remote attackers to execute arbitrary code. The continuation-token restoration path deserializes a caller-supplied token as a Python object without authenticity or type validation. Exploitation requires an application to process an attacker-controlled continuation token; no authentication or user interaction is required.
The record
- CVE
- CVE-2026-21531
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo