OpenStack Mistral through 22

CVE-2026-41283 is an authorization failure in OpenStack Mistral where several API endpoints fail to enforce policy correctly. Per the OpenStack advisory, affected versions are >=20.0.0 <20.1.1, ==21.0.0, and ==22.0.0; any authenticated user who can reach the Mistral API can create public resources and upload arbitrary code that later runs on Mistral executor workers, with potential theft of service credentials from those workers.

The vendor's 9.9 CRITICAL score captures the *impact* once exploited, but it overstates the *reachability* for most enterprises. This is not unauthenticated edge RCE: the attacker needs a valid authenticated user context plus API reachability to a relatively niche OpenStack component that is often internal-only, but if those two conditions are met the blast radius can jump from one tenant foothold to cloud service credentials fast.

Why this verdict

• Downgraded for attacker position: vendor 9.9 assumes the damage path, but exploitation requires authenticated remote access (PR:L), which means the attacker already has a foothold or valid tenant identity.
• Downgraded for exposure population: Mistral is a specialized OpenStack workflow service, not a ubiquitous edge service, and many enterprises keep it on internal/controller networks rather than public internet.
• Kept HIGH for blast radius: once exploited, this is not a cosmetic RBAC miss; it becomes arbitrary code execution on executor workers with potential service credential theft and cross-service pivoting.

Why not higher?

It is not an unauthenticated internet-edge flaw, and the affected component is not broadly exposed in the same way as VPNs, firewalls, or webmail. The prerequisite chain compounds downward pressure: valid account, Mistral deployed, Mistral reachable, and workers carrying useful credentials.

Why not lower?

The post-exploit impact is too strong for MEDIUM. An ordinary authenticated user can allegedly turn authorization gaps into code execution on control-plane-adjacent workers, and stolen service credentials can widen impact far beyond the original tenant account.

1. Restrict Mistral API reachability — Put the Mistral API behind admin-only or internal-only network paths immediately, and where possible remove tenant/user access until patched. For a HIGH verdict, deploy this compensating control within 30 days; if you have evidence of abuse, treat it as immediate emergency containment.
2. Disable or gate public resource creation — If your deployment allows policy overrides or API gateway rules, block non-admin creation of public workflows/actions/environments and other upload-capable endpoints. This directly targets the advisory's exploit path and should be in place within 30 days if patching is delayed.
3. Reduce executor credential value — Rotate and narrow service credentials available to Mistral workers, and remove unused cloud-wide privileges from the worker context. This does not stop code execution, but it sharply reduces the pivot value if exploitation occurs; complete within 30 days.
4. Hunt for suspicious Mistral object creation — Query audit/API logs for new public workflows, actions, environments, or definitions created by low-privilege users, especially identities that rarely use Mistral. Stand up this detection within 30 days while patch rollout proceeds.

Run this on the target Mistral host or in the service venv/container where the mistral Python package is installed. Invoke as bash check-cve-2026-41283.sh; no root is required if the Python environment is readable, though root may be needed on locked-down appliances. The script prints VULNERABLE, PATCHED, or UNKNOWN and exits 0, 1, or 2 respectively.

#!/usr/bin/env bash
# check-cve-2026-41283.sh
# Determine likely exposure to CVE-2026-41283 based on installed OpenStack Mistral version.
# Exit codes: 0=VULNERABLE, 1=PATCHED, 2=UNKNOWN

set -u

PYTHON_BIN="${PYTHON_BIN:-python3}"

get_version() {
  "$PYTHON_BIN" - <<'PY'
import sys
try:
    try:
        from importlib.metadata import version
    except Exception:
        from importlib_metadata import version  # type: ignore
    print(version("mistral"))
except Exception:
    sys.exit(1)
PY
}

ver_cmp_py='from packaging.version import Version as V
import sys
v=V(sys.argv[1])
expr=sys.argv[2]
if expr=="lt": sys.exit(0 if v < V(sys.argv[3]) else 1)
elif expr=="le": sys.exit(0 if v <= V(sys.argv[3]) else 1)
elif expr=="eq": sys.exit(0 if v == V(sys.argv[3]) else 1)
elif expr=="ge": sys.exit(0 if v >= V(sys.argv[3]) else 1)
elif expr=="gt": sys.exit(0 if v > V(sys.argv[3]) else 1)
else: sys.exit(2)'

ver_test() {
  "$PYTHON_BIN" -c "$ver_cmp_py" "$1" "$2" "$3"
}

VERSION="$(get_version 2>/dev/null || true)"
if [ -z "$VERSION" ]; then
  echo "UNKNOWN - Python package 'mistral' not found in current environment"
  exit 2
fi

# Known affected ranges from OSSA-2026-020:
# >=20.0.0 <20.1.1, ==21.0.0, ==22.0.0
if ver_test "$VERSION" ge "20.0.0" && ver_test "$VERSION" lt "20.1.1"; then
  echo "VULNERABLE - installed mistral version $VERSION is in affected range >=20.0.0 <20.1.1"
  exit 0
fi

if ver_test "$VERSION" eq "21.0.0"; then
  echo "VULNERABLE - installed mistral version $VERSION matches affected version 21.0.0"
  exit 0
fi

if ver_test "$VERSION" eq "22.0.0"; then
  echo "VULNERABLE - installed mistral version $VERSION matches affected version 22.0.0"
  exit 0
fi

# If version is below 20.0.0, unaffected per advisory ranges we have.
if ver_test "$VERSION" lt "20.0.0"; then
  echo "PATCHED - installed mistral version $VERSION is below the published affected ranges"
  exit 1
fi

# Anything newer than the exact vulnerable singletons is treated as patched,
# but note that public release tags for all maintenance lines may lag advisory publication.
if ver_test "$VERSION" ge "20.1.1"; then
  if ! ver_test "$VERSION" eq "21.0.0" && ! ver_test "$VERSION" eq "22.0.0"; then
    echo "PATCHED - installed mistral version $VERSION is not in the published affected ranges"
    exit 1
  fi
fi

echo "UNKNOWN - unable to confidently classify mistral version $VERSION"
exit 2

Sources

1. OpenStack oss-sec advisory OSSA-2026-020
2. OpenStack Mistral releases page
3. OpenStack releases home / lifecycle status
4. OpenStack Mistral install documentation
5. OpenStack Mistral release notes index
6. CISA Known Exploited Vulnerabilities Catalog
7. FIRST EPSS program
8. Red Hat OpenStack Platform 17.1 upgrade framework mentioning deprecated Mistral services