Use of Less Trusted Source Affecting zaqar package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-ECHOLATEST-ZAQAR-20138326
- published25 Sept 2026
- disclosed24 Sept 2026
Introduced: 24 Sep 2026
NewCVE-2026-97404 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest zaqar.
NVD Description
Note: Versions mentioned in the description apply only to the upstream zaqar package and not the zaqar package as distributed by Echo.
See How to fix? for Echo:latest 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.