Azure Core is vulnerable to deserialization of untrusted dataGHSA-jm66-cg57-jjv5
HIGHGHSA-jm66-cg57-jjv5 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in azure-core. A fix is available for azure-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- 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 GHSA-jm66-cg57-jjv5.
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-coreReal-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 Azure Core shared client library for Python allows an authorized attacker to execute code over a network.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | azure-core | all versions | 1.38.0pip install --upgrade 'azure-core==1.38.0' |
Affected Products
azure core shared client librarymicrosoftDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for azure-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update azure-core to 1.38.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jm66-cg57-jjv5 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
azure-core 1.30.0 is bundled in the Ansible Automation Platform 2.6 controller image, observed in the awx venv. azure-core is a bundled PyPI dependency pulled in by the Azure Ansible content (azure.azcollection) and other Azure SDK clients across several AAP execution environments; but it is not Red Hat source code.
No code-level mitigation is provided by Red Hat. Exploitation requires an authorized actor to supply crafted serialized data to an Azure deserialization code path. Until an execution environment shipping azure-core 1.38.0 or later is available, limit which users can create and run Azure-related automation (azure.azcollection jobs), restrict network access to the controller and execution environments to trusted operators, and remove the Azure collections/ azure-core from environments that do not use Azure automation.Source: Red Hat security advisory for GHSA-jm66-cg57-jjv5 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-jm66-cg57-jjv5 in your dependencies?
Find it across PyPI, including transitive dependencies.