Skip to main content
VulnerabilityPublished Updated

CVE-2026-43000: OpenStack Keystone · Incorrect Authorization

Affects OpenStack KeystoneSource CVE Database V5

0
Compare

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, 11:52 UTC

CVSS 3.1 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade OpenStack Keystone to 29.0.2, 28.0.2 or 27.0.2.

Affected software

ProductAffectedFixed in
OpenStackKeystoneAffected
  • >=29.0.0 <29.0.2
Fixed in
  • 29.0.2
OpenStackKeystoneAffected
  • >=28.0.0 <28.0.2
Fixed in
  • 28.0.2
OpenStackKeystoneAffected
  • >=14.0.0 <27.0.2
Fixed in
  • 27.0.2

AI-suggested

The vulnerability affects OpenStack Keystone versions prior to 29.0.2. Users should monitor the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-43000 for updates on patches or official fixes. If you cannot patch yet, restrict the use of application credentials and trusts to trusted users only and review role assignments carefully to limit potential abuse.

Description

An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim's identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim's actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim's admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim's identity.

References

Community reviews

Loading reviews…