cve.bz

CVE-2026-40214 openstack cyborg: Improper Ownership Management

6.3 mediumEPSS 0.2%Fix available

Medium (6.3) in openstack cyborg. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in openstack-cyborg 16.0.1.

On this page
In OpenStack Cyborg before 16.0.1, the Accelerator Request (ARQ) API does not enforce project ownership at any layer. The project_id column in the database is never populated (NULL for every ARQ), database queries have no project filtering, and policy checks are self-referential (the authorize_wsgi decorator compares the caller's project_id 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.

Severity

CVSS 3.1

6.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-282 Improper Ownership Management
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40214 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40214?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40214?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40214 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40214

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40214](https://cve.bz/cve/badge/CVE-2026-40214.svg)](https://cve.bz/cve/CVE-2026-40214)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40214"><img src="https://cve.bz/cve/badge/CVE-2026-40214.svg" alt="CVE-2026-40214"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenStack Cyborgfrom 3.0.0 before 14.0.1
OpenStack Cyborgfrom 15.0.0 before 15.0.1
OpenStack Cyborgfrom 16.0.0 before 16.0.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mmpc-xjxr-5hf8PyPIopenstack-cyborg<16.0.116.0.1
PYSEC-2026-2854PyPIopenstack-cyborg<16.0.116.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13cyborg14.0.0-3+deb13u1DEBIAN-CVE-2026-40214
Debian14cyborg16.0.0+git+2026.04.26.b8edfa06f1-1DEBIAN-CVE-2026-40214
Ubuntu25.10cyborg14.0.0-3+deb13u1build0.25.10.1UBUNTU-CVE-2026-40214 USN-8413-1
Ubuntu26.04:LTScyborg16.0.0-2ubuntu0.1UBUNTU-CVE-2026-40214 USN-8413-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON