CVE-2026-41283
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenStack 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenStack Mistral through version 22.0.0 contains a critical vulnerability where certain API endpoints permit arbitrary remote code execution when exposed. Attackers can exploit these endpoints to execute commands on the underlying system and exfiltrate service credentials, potentially compromising the entire OpenStack environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Mistral versionRun 'mistral --version' or check the installed package version via 'pip show mistral' or your package manager (e.g., 'rpm -q mistral' or 'dpkg -l mistral')Affected if The installed version is 22.0.0 or any earlier version (e.g., 21.x, 20.x, older)
-
Verify Mistral API network exposureCheck your firewall rules, security groups, or load balancer configuration to determine if the Mistral API service (typically port 8989) is accessible from untrusted/external networks. Look for rules allowing inbound traffic from 0.0.0.0/0 or non-internal subnets to the Mistral port.Affected if The Mistral API port is open to untrusted or public networks without IP-based restrictions
-
Confirm Keystone authentication enforcementInspect Mistral configuration files (typically /etc/mistral/mistral.conf or environment variables) to verify that 'auth_enable = True' is set and that the 'auth_type' is configured to require Keystone tokens. Check that endpoints are registered in Keystone and require valid authentication.Affected if Authentication is disabled or set to 'noauth'/'basic' mode, or if API endpoints accept requests without valid Keystone tokens
-
Review API endpoint access controlsExamine Mistral's API endpoint definitions and policy.json file (usually /etc/mistral/policy.json) to verify that execution creation endpoints enforce RBAC and do not allow anonymous or unauthenticated access.Affected if Policy.json allows 'admin' or 'creator' roles to anonymous users, or if there are no role checks on vulnerable endpoints
You are affected if Mistral version is 22.0.0 or earlier AND the API is exposed to untrusted networks without proper Keystone token authentication enforcement on all endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict Mistral API exposure to internal networks only, implement strong authentication, and monitor for unauthorized access attempts; when a patched version becomes available, upgrade immediately.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41283 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data