CVE-2026-42999: OpenStack Keystone · Incorrect Authorization
Affects OpenStack KeystoneSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 29.0.2 : update OpenStack Keystone when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 29.0.2, 28.0.2, 27.0.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade OpenStack Keystone to 29.0.2, 28.0.2 or 27.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenStackKeystone | Affected
| Fixed in
|
| OpenStackKeystone | Affected
| Fixed in
|
| OpenStackKeystone | Affected
| Fixed in
|
PyPIkeystonepkg:pypi/keystoneOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in OpenStack Keystone version 29.0.2. Users should upgrade to version 29.0.2 or later to remediate this issue. Until patched, restrict authenticated user permissions to minimize risk and monitor for unusual access patterns related to Keystone API usage. Refer to the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-42999 for official guidance.
Description
An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone RBAC policy enforcer in enforce_call unconditionally merges the raw JSON request body into the policy enforcement dictionary via policy_dict.update(json_input.copy()), overwriting trusted target data that was previously set from database lookups. Because flask.request.get_json is called with force=True, this works regardless of Content-Type or HTTP method. Any authenticated user can inject arbitrary policy target attributes (e.g., user_id, project_id) into the request body to bypass RBAC checks and perform unauthorized operations on resources belonging to other users or projects. This was introduced in commit 5ea59f52 (Rocky/14.0.0).
References
- bugs.launchpad.net/keystone/+bug/2148398 (opens in a new tab)
- security.openstack.org/ossa/OSSA-2026-015.html (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-42999 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2482840 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42999.json (opens in a new tab)