GHSA-9hfw-w3f4-c4p8 — mistral
CRITICALGHSA-9hfw-w3f4-c4p8 is a critical-severity (CVSS 9.9) CWE-863 vulnerability in mistral. A fix is available for mistral — see the affected versions and patch details below.
OpenStack Mistral allows Arbitrary Remote Code Execution when the API is exposed
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-9hfw-w3f4-c4p8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-9hfw-w3f4-c4p8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
mistral🐍mistral🐍mistralReal-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
OpenStack Mistral through 22.0.0 allows Arbitrary Remote Code Execution when the API is exposed. There are endpoints that allow code execution, which can lead to exfiltration of service credentials.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | mistral | ≥ 20.0.0&&< 20.1.1 | 20.1.1pip install --upgrade 'mistral==20.1.1' |
| 🐍PyPI | mistral | all versions | No fix |
| 🐍PyPI | mistral | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mistral, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mistral to 20.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hfw-w3f4-c4p8 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
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.
Restrict network access to the OpenStack Mistral API to trusted internal networks or hosts. Configure firewall rules to limit inbound connections to the Mistral API port (typically 8989) from untrusted sources, ensuring the API is not exposed to the public internet. Example using `firewall-cmd` (adjust zones and ports as needed): `firewall-cmd --zone=public --remove-port=8989/tcp --permanent` `firewall-cmd --zone=internal --add-port=8989/tcp --permanent` `firewall-cmd --reload` This action may impact legitimate clients requiring external access to the Mistral API. A service reload or restart may be required for firewall changes to take full effect.Source: Red Hat security advisory for GHSA-9hfw-w3f4-c4p8 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-9hfw-w3f4-c4p8 in your dependencies?
Find it across PyPI, including transitive dependencies.