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.
CVE-2026-97404
This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.2
- EG Score
- 9.2(low)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity92% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (1)
Auto-updated Sep 24, 2026Bug #2164987 “[OSSA-2026-042] Empty URL-Signature header bypasse...” : Bugs : zaqar
https://launchpad.net/bugs/2164987Vendor Advisories for CVE-2026-97404(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 09:55 UTCGHSA enrichment
- 2026-09-25 05:42 UTCGHSA enrichment
- 2026-09-25 01:29 UTCGHSA enrichment
- 2026-09-24 21:15 UTCGHSA enrichment
- 2026-09-24 19:36 UTCGHSA enrichment
- 2026-09-24 15:28 UTCEG score recompute
- 2026-09-24 14:48 UTCEG score recompute
- 2026-09-24 14:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-97404?
When was CVE-2026-97404 disclosed?
What is the CVSS score of CVE-2026-97404?
How do I remediate CVE-2026-97404?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-97404
Is Your Infrastructure Affected by CVE-2026-97404?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.