Skip to content
Fencer Intel
medium 6.0

CVE-2026-93861 json

In OpenStack Mistral through 23.0.0, the workflow membership API lets a project that has accepted a share of another project's private work…

published last mo. modified 27d ago also EUVD-2026-95131

cvss
6.0
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

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.

Patch / fix

  • OpenStack Mistral 20.1.1, 21.0.1, 22.0.1
  • mistral Debian 14 23.0.0-2

debian advisories DEBIAN-CVE-2026-93861

Is CVE-2026-93861 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-93861 updated cvss 5.4

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

  • Red Hat OpenStack Platform 13 (Queens) python-mistral, openstack-mistral, python-mistral-tests, openstack-mistral-all, openstack-mistral-api, openstack-mistral-common, +3 more
    affected: workaround, no fix planned “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.”
  • Red Hat OpenStack Platform 16.2 python3-mistral, openstack-mistral-all, openstack-mistral-api, openstack-mistral-common, openstack-mistral-engine, openstack-mistral-executor, +2 more
    affected: workaround, no fix available “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
27d ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 4.0 6.0 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
CNA 4.0 6.0 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • OpenStack Mistral

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.