CVE-2026-107363

Published Oct 7, 2026 CVSS 4.0 · 6.1 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in OpenStack Zaqar allows an authenticated user with a valid Keystone token for one project to substitute another project's UUID in WebSocket requests. This oversight permits enumeration, inspection, creation, or deletion of queues belonging to a different project, thereby exposing, tampering with, or deleting queue data. The weakness stems from improper validation of the project identifier in subsequent WebSocket requests, identified as CWE‑472.

Affected Systems

OpenStack Zaqar deployments using the WebSocket transport with Keystone authentication, prior to version 23.0.1, are affected. The issue is confined to environments where WebSocket transport is enabled and Keystone token authentication is in use.

Risk and Exploitability

The vulnerability carries a CVSS score of 6.1, indicating a moderate impact. Its EPSS score is not available, and it is not listed in CISA’s KEV catalog, suggesting limited commercial exploitation so far. An attacker requiring an authenticated Keystone token for one project can exploit the flaw by forging a different project’s UUID in WebSocket requests, potentially from a remote location. The attack requires network connectivity to the Zaqar WebSocket endpoint and knowledge of target project identifiers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenStack Zaqar to version 23.0.1 or later.
  • Disable or restrict the WebSocket transport in Zaqar configuration if it is not required for your deployment.
  • Configure access controls to ensure Keystone tokens are scoped to the intended project and monitor the logs for unauthorized queue operations.

Generated by OpenCVE AI on October 7, 2026 at 21:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4912-1 zaqar security update
History
Type Values Removed Values Added
First Time appeared Openstack
Openstack zaqar
Vendors & Products Openstack
Openstack zaqar
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Weaknesses CWE-472
References
Metrics cvssV4_0

{'score': 6.1, 'vector': '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'}

Weaknesses
  • CWE-472

    External Control of Assumed-Immutable Web Parameter

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Oct 7, 2026, 11:06 PM
Reserved
Oct 7, 2026, 8:08 PM
Status
Awaiting Analysis
Published
Oct 7, 2026, 9:17 PM
Modified
Oct 8, 2026, 9:33 PM