Quick answers
- Is CVE-2026-97404 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97404 being exploited in the wild.
- How severe is CVE-2026-97404?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- OpenStack Zaqar 1.0.0 to 20.1.1, 21.0.0 to 21.0.1, 22.0.0 to 22.0.1.
- Is there a fix for CVE-2026-97404?
- A patch was published on 2026-09-24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97404 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-97404?
- Check whether you run OpenStack Zaqar at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WSGI transport's SignedHeadersAuth middleware checks if the URL-Signature header is None to choose between Keystone auth and pre-signed URL path; an empty string passes this check (not None) and reaches pre-signed URL verification. The verify_pre_signed_url function uses a falsy check ("if not signature") which treats empty string as falsy and returns early without performing HMAC validation. An unauthenticated remote attacker with knowledge of a target project UUID can exploit this with a crafted HTTP request, bypassing both authentication layers. The websocket transport is unaffected. Patches are available for versions 20.1.2, 21.0.2, 22.0.2 and later.
Affected products
- OpenStack Zaqar 1.0.0 to 20.1.1, 21.0.0 to 21.0.1, 22.0.0 to 22.0.1
Timeline
- 2026-09-24: disclosed
- 2026-09-24: patched