OpenStack is core cloud infrastructure used broadly; this unauthenticated auth-bypass can expose/modify tenant queues and enable admin operations, risking widespread service and data compromise.
CVE-2026-97404
OpenStack Zaqar WSGI auth bypass via empty URL-Signature header
Is CVE-2026-97404 being exploited?
Not confirmed. CVE-2026-97404 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-97404?
CVE-2026-97404 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-97404?
Yes. A fix has been recorded for CVE-2026-97404. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-97404 affect?
CVE-2026-97404 affects OpenStack Zaqar < 22.0.2 (WSGI transport), OpenStack deployments using Zaqar with an authentication strategy, Zaqar admin_mode deployments (pools/flavors). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-97404?
Upgrade Zaqar to 22.0.2 or apply vendor patch; restrict/limit access to Zaqar endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker bypasses Keystone and presigned-URL checks to read, enumerate, create, delete project queues/messages/claims/subscriptions; may perform admin ops (manage pools/flavors).
Immediate action required
- affected>= 1.0.0 and < 20.1.2
- affected>= 21.0.0 and < 21.0.2
- affected>= 22.0.0 and < 22.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 26 Sept 2026 (SSVC 2.0.3).
timeline
- 24 Sept 2026Published
- 25 Sept 2026Analysed by vulneraibility.com · 1 day later
- 26 Sept 2026CISA SSVC assessment: exploitation none · 1 day later
- 26 Sept 2026CVE record last updated · same day later
- Linklaunchpad.net /bugs/2164987
- Linkopenwall.com /lists/oss-security/2026/09/24/6
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.