CVE-2026-93861

openstack-mistral: mistral: workflow membership sub-delegation allows unauthorized access grant to private workflows

Published Oct 8, 2026 CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
Description
In OpenStack Mistral through 23.0.0, the workflow membership API lets a project that has accepted a share of another project's private workflow create a further membership naming a third project. The new membership row is created with its project_id defaulted to the accepting project rather than the original workflow owner, and thus the owner can neither see nor delete it. The third project can accept this membership (that it had not actually been granted by the owner), and then read and execute the owner's private workflow; only the accepting (not the owning) project can later revoke that access.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Title Misassigned Workflow Membership Enables Unauthorized Access to Private Workflows in OpenStack Mistral openstack-mistral: mistral: workflow membership sub-delegation allows unauthorized access grant to private workflows
Weaknesses CWE-862
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Openstack
Openstack mistral
Vendors & Products Openstack
Openstack mistral
Type Values Removed Values Added
Title Misassigned Workflow Membership Enables Unauthorized Access to Private Workflows in OpenStack Mistral
Type Values Removed Values Added
Description In OpenStack Mistral through 23.0.0, the workflow membership API lets a project that has accepted a share of another project's private workflow create a further membership naming a third project. The new membership row is created with its project_id defaulted to the accepting project rather than the original workflow owner, and thus the owner can neither see nor delete it. The third project can accept this membership (that it had not actually been granted by the owner), and then read and execute the owner's private workflow; only the accepting (not the owning) project can later revoke that access.
Weaknesses CWE-863
References
Metrics cvssV4_0

{'score': 6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Oct 15, 2026, 6:10 PM
Reserved
Sep 18, 2026, 7:15 PM
Status
Deferred
Published
Oct 8, 2026, 6:18 PM
Modified
Oct 15, 2026, 7:17 PM
Severity
Moderate
Public date
Oct 8, 2026, 7:17 PM