All reports
Medium

zaqar: OpenStack Zaqar: authentication bypass via empty URL-Signature header

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-97404

Probability of exploitation in the next 30 days: 0.27%

FIRST EPSS · 2026-11-20

Description

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.

A flaw was found in OpenStack Zaqar. An unauthenticated remote attacker who knows a target project's identifier can bypass authentication by sending an HTTP request containing an empty URL-Signature header to the Web Server Gateway Interface (WSGI) transport. Successful exploitation allows the attacker to read, create, or delete message queues, messages, and subscriptions, as well as perform unauthorized administrative operations.