Skip to content
Fencer Intel
high 8.3

CVE-2026-42999 json

OpenStack Keystone has an Authorization Bypass

published 5mo ago modified 14d ago also GHSA-2r23-2g6v-2m5f , PYSEC-2026-600 , EUVD-2026-33241

cvss
8.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

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).

Patch / fix

  • pypi keystone 27.0.2, 28.0.2, 29.0.2
  • OpenStack Keystone 27.0.2, 28.0.2, 29.0.2
  • keystone Debian 12 2:22.0.2-0+deb12u3
  • keystone Debian 13 2:27.0.0-3+deb13u4
  • keystone Debian 14 2:29.0.1-2

debian advisories DEBIAN-CVE-2026-42999

  • keystone Ubuntu 22.04 LTS 2:21.0.1-0ubuntu2.4
  • keystone Ubuntu 24.04 LTS 2:25.0.0-0ubuntu1.4
  • keystone Ubuntu 25.10 2:28.0.0-0ubuntu1.3
  • keystone Ubuntu 26.04 LTS 2:29.0.0-0ubuntu1.2

ubuntu advisories UBUNTU-CVE-2026-42999

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-42999 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-42999 updated cvss 8.3

openstack-keystone: OpenStack Keystone: Unauthorized access and privilege escalation via arbitrary policy attribute injection

  • Red Hat OpenStack Platform 13 (Queens) rhosp13/openstack-keystone Red Hat OpenStack Platform 16.2 python3-keystone, openstack-keystone, rhosp-rhel8/openstack-keystone Red Hat OpenStack Platform 17.1 python3-keystone, openstack-keystone, rhosp-rhel9/openstack-keystone Red Hat OpenStack Platform 18.0 openstack-keystone, rhoso/openstack-keystone-rhel9
    affected: no fix available
  • Red Hat OpenStack Platform 13 (Queens) python-keystone, openstack-keystone
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.launchpad.net https://bugs.launchpad.net/keystone/+bug/2148398 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
CISA ADP 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
GitHub 3.1 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi keystone
>=14.0.0, <27.0.2
>=28.0.0, <28.0.2
>=29.0.0, <29.0.2
27.0.2
28.0.2
29.0.2

Affected products

  • OpenStack Keystone
  • Red Hat Red Hat OpenStack Platform 13 (Queens)
  • Red Hat Red Hat OpenStack Platform 16.2
  • Red Hat Red Hat OpenStack Platform 17.1
  • Red Hat Red Hat OpenStack Platform 18.0

Classification

Weakness
  • CWE-863 Incorrect Authorization
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.