# CVE-2026-107363: Missing authorization in Zaqar

> Authenticated users can access other projects' queues via WebSocket transport, leading to unauthorized data disclosure and modification.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107363, GHSA-hc4w-8h6h-frmg, UBUNTU-CVE-2026-107363

## What is CVE-2026-107363?

CVE-2026-107363 is a medium-severity missing authorization vulnerability in OpenStack Zaqar, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenStack Zaqar before 23.0.1, the WebSocket transport fails to bind the project identifier in subsequent requests to the project authenticated by the Keystone token. An authenticated user with a valid token for one project may substitute another project's UUID to enumerate, inspect, create, or delete queues belonging to that project, resulting in unauthorized disclosure, modification, or loss of queue data. Only deployments using the WebSocket transport with Keystone authentication are affected.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

## Which versions are affected by CVE-2026-107363?


## How do I fix CVE-2026-107363?

Upgrade to a fixed version.

## Is CVE-2026-107363 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107363 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107363 and fix it if it is affected.

What it is: CVE-2026-107363 is a medium-severity missing authorization vulnerability in OpenStack Zaqar, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107363 exists.

Affected product: OpenStack Zaqar. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107363/ (Markdown: https://insights.sbomify.com/CVE-2026-107363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107363
- OSV: https://osv.dev/vulnerability/CVE-2026-107363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107363/
Summaries are generated and may contain mistakes; the official description above is the record.