Quick answers
- Is CVE-2026-40213 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40213 being exploited in the wild.
- How severe is CVE-2026-40213?
- High severity, with a CVSS score of 7.4, published 7 May 2026.
- Which products and versions are affected?
- OpenStack Cyborg >=3.0.0 <14.0.1, >=15.0.0 <15.0.1, >=16.0.0 <16.0.1; openstack-cyborg (PyPI) < 16.0.1, ECOSYSTEM:introduced=0,fixed=16.0.1.
- Is there a fix for CVE-2026-40213?
- Yes. openstack-cyborg (PyPI): upgrade to 16.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40213 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-40213?
- Check whether you run OpenStack Cyborg or openstack-cyborg (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- openstack-cyborg (PyPI): upgrade to 16.0.1 or later
pip install "openstack-cyborg>=16.0.1"
Technical details
OpenStack Cyborg before 16.0.1 (and various backported versions) uses 'rule:allow' (check_str='@') as the default policy for multiple API endpoints, including device, deployable, and attribute management. This configuration causes oslo.policy to evaluate authorization as an unconditional 'True' for any request containing a valid Keystone token, ignoring roles, project membership, or scope. An authenticated attacker with no assigned roles can exploit this via the network to enumerate hardware topology, reprogram FPGA bitstreams via agent RPC, or manipulate hardware metadata. The vulnerability is addressed by replacing the permissive default with 'rule:admin_api' or 'rule:project_member_or_admin' as appropriate.
Affected products
- OpenStack Cyborg >=3.0.0 <14.0.1, >=15.0.0 <15.0.1, >=16.0.0 <16.0.1
Identifiers
- CVE-2026-40213
- GHSA-mm7j-mhhj-hj36
- PYSEC-2026-2853
Timeline
- 2026-03-04: disclosed: Bug reported to OpenStack by Sean Mooney
- 2026-05-07: advisory: OSSA-2026-011 published
- 2026-05-08: patched: GitHub advisory published for version 16.0.1