Use of Less Trusted Source Affecting openstack-zaqar package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.27% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-OPENSTACKZAQAR-21090404
  • published16 Oct 2026
  • disclosed24 Sept 2026

Introduced: 24 Sep 2026

NewCVE-2026-97404  (opens in a new tab)
CWE-348  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 openstack-zaqar.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openstack-zaqar package and not the openstack-zaqar package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.