CVE-2026-107363
Description
A flaw was found in OpenStack Zaqar. In deployments utilizing the WebSocket transport, the service fails to bind subsequent communication requests to the project associated with the authenticated user's token. An authenticated remote attacker can substitute a target project's identifier to inspect, create, modify, or delete message queues belonging to another project. This issue results in unauthorized cross-project data disclosure, tampering, or loss of message queue data.
Statement
Red Hat rates the security impact of this vulnerability as Important rather than Critical because exploitation requires valid tenant authentication and knowledge of the target project's identifier, yet enables breaking cross-tenant isolation boundaries. Deployments that utilize OpenStack Zaqar with Keystone authentication over the WebSocket transport allow a tenant to manipulate queue resources belonging to other tenants. Environments relying exclusively on the standard HTTP REST transport are not impacted.
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control
Technical Impact: Gain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
