Skip to main content
VulnerabilityPublished

CVE-2026-33551: OpenStack Keystone · Incorrect Authorization

Affects OpenStack KeystoneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.5 Low : upgrade to 26.1.1 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.1.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Apr 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 29 Oct 2026.

What to do

Upgrade OpenStack Keystone to 26.1.1.

Affected software

ProductAffectedFixed in
OpenStackKeystoneAffected
  • >=14.0.0 <26.1.1
  • =27.0.0
  • =28.0.0
  • =29.0.0
Fixed in
  • 26.1.1

AI-suggested

A patch is available for this vulnerability. Since this affects OpenStack Keystone as a cloud service, the vendor typically manages remediation server-side. Users should verify with the OpenStack vendor advisory for the application of the official fix or upgrade to patched versions (26.1.1 or later, 27.0.0+, 28.0.0+, 29.0.0+ as applicable). Deployments not using restricted application credentials with the EC2/S3 compatibility API are not affected. Patch status is confirmed as available; apply updates promptly to mitigate this issue.

Description

An issue was discovered in OpenStack Keystone 14 through 26 before 26.1.1, 27.0.0, 28.0.0, and 29.0.0. Restricted application credentials can create EC2 credentials. By using a restricted application credential to call the EC2 credential creation API, an authenticated user with only a reader role may obtain an EC2/S3 credential that carries the full set of the parent user's S3 permissions, effectively bypassing the role restrictions imposed on the application credential. Only deployments that use restricted application credentials in combination with the EC2/S3 compatibility API (swift3 / s3api) are affected.

References

Community reviews

Loading reviews…