Medium · CVSS 6.1CVE-2026-107363

CISA ADP VulnrichmentCVE-2026-107363

Answer in brief

CVE-2026-107363 records a Medium severity (CVSS 6.1) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps OpenStack/Zaqar (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 7, 2026Updated Oct 7, 2026Source checked Oct 7, 2026First seen by HOL Oct 7, 2026Material review Oct 7, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenStack/Zaqar (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenStack/Zaqargeneric	>=1.0.0 <20.1.3 \|\| >=21.0.0 <21.0.3 \|\| >=22.0.0 <22.0.3 \|\| >=23.0.0 <23.0.1	20.1.3, 21.0.3, 22.0.3, 23.0.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenStack/Zaqar.
Review the reported fix. Update OpenStack/Zaqar to 20.1.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 7, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.