OpenStack Cyborg's Accelerator Request (ARQ) API does not enforce project ownership at any layer

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2026-40214: 0.21% estimated exploitation activity in the next 30 days; percentile 10.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In OpenStack Cyborg before 16.0.1, the Accelerator Request (ARQ) API does not enforce project ownership at any layer. The projectid column in the database is never populated (NULL for every ARQ), database queries have no project filtering, and policy checks are self-referential (the authorizewsgi decorator compares the caller's projectid with itself rather than the target resource). Any authenticated non-admin user can complete various actions such as deleting ARQs bound to other projects' instances, aka cross-tenant denial of service.

Published by the source

8 May 2026, 00:31 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mmpc-xjxr-5hf8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mmpc-xjxr-5hf8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-40214

Advisory: OpenStack Cyborg's Accelerator Request (ARQ) API does not enforce project ownership at any layer
IDs: CVE-2026-40214, GHSA-mmpc-xjxr-5hf8
Record: https://patchnext.com/advisories/cve-2026-40214 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openstack-cyborg 16.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI openstack-cyborg: affected < 16.0.1; fixed in 16.0.1

## Suggested inspection (read-only)
- `python -m pip show openstack-cyborg`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openstack-cyborg.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mmpc-xjxr-5hf8 (OSV record GHSA-mmpc-xjxr-5hf8 lists affected ranges: PyPI openstack-cyborg >=0 <16.0.1 (fixed))
- Verified: https://github.com/advisories/GHSA-mmpc-xjxr-5hf8 (GitHub-reviewed advisory GHSA-mmpc-xjxr-5hf8 lists affected ranges: PyPI openstack-cyborg >=0 <16.0.1)

Commands are suggestions: review each one before running it.