CVE-2026-93860 OpenStack CVE debrief

Who should care

Operators and administrators of OpenStack Mistral should assess their exposure and prioritize verification of their systems to ensure that only authorized users can access and modify the maintenance state. This includes reviewing current configurations, validating affected scope, and implementing necessary security measures to prevent unauthorized access. Additionally, security teams and vulnerability management teams should be informed to ensure a timely

Why it matters

CVE-2026-93860 allows unauthorized access to OpenStack Mistral's cluster-wide maintenance state, potentially disrupting service operations. Operators and administrators should verify their systems and restrict access to authorized users.

• Potential unauthorized access to cluster-wide maintenance state.
• Possible disruption of new workflow and execution objects across all tenant projects.
• Need for verification of OpenStack Mistral versions and configurations.
• Requirement for restricted access to the /v2/maintenance API controller.

Technical summary

The /v2/maintenance API controller in OpenStack Mistral through 23.0.0 clears the request context and calls the maintenance service directly without policy enforcement, allowing any holder of a valid Mistral token to read and change the service's cluster-wide maintenance state. This unauthorized access could lead to disruption of service operations and impact tenant projects. The vulnerability highlights the need for strict access controls and regular security audits to prevent similar issues in the future. Operators and administrators should verify their systems and restrict access to authorized users.

Defensive priority

Operators and administrators of OpenStack Mistral should assess exposure and prioritize verification of their systems, focusing on ensuring that only authorized users can access and modify the maintenance state.

Recommended defensive actions

• Verify and restrict access to the /v2/maintenance API controller to only authorized users.
• Review and update OpenStack Mistral versions to ensure they are not affected.
• Monitor for any unauthorized changes to the maintenance state.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source item provide details on the vulnerability in OpenStack Mistral, including its description and affected versions. However, additional information on exploitation or specific impacts is limited.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.