CVE-2026-97404
CriticalCVSS 9.2Summary
In OpenStack Zaqar before 22.0.2, the WSGI transport mishandles the URL-Signature header. By sending a request with an empty URL-Signature header, an unauthenticated remote attacker who knows a target project's UUID may bypass both Keystone authentication and pre-signed URL verification, resulting in the ability to read, enumerate, create, and delete that project's queues, messages, claims, and subscriptions. By additionally claiming an administrative role, the attacker may also perform administrative operations, such as managing pools and flavors in admin_mode deployments. Only deployments using the WSGI transport with an authentication strategy configured are affected; the websocket transport is not affected.
Risk Assessment
An unauthenticated attacker who knows a project's UUID can gain full access to that project's queues and messages, and in some cases perform administrative operations. This can lead to data leakage, modification, or loss of service availability.
Recommendation
Update OpenStack Zaqar to version 22.0.2 or later. If possible, consider switching to the websocket transport or restricting network access to the WSGI interface.
Other vulnerabilities in OpenStack Zaqar
Original NVD description (English source)
In OpenStack Zaqar before 22.0.2, WSGI transport mishandles the URL-Signature header. By sending a request with an empty URL-Signature header, an unauthenticated remote attacker who knows a target project's UUID may bypass both Keystone authentication and pre-signed URL verification, resulting in the ability to read, enumerate, create, and delete that project's queues, messages, claims, and subscriptions. By additionally claiming an administrative role, the attacker may also perform administrative operations, such as managing pools and flavors in admin_mode deployments. Only deployments using the WSGI transport with an authentication strategy configured are affected; the websocket transport is not affected.