# CVE-2026-33551: OpenStack Keystone: Restricted application credentials can create EC2 credentials

> Authenticated users with reader roles can bypass application credential restrictions to obtain full S3 permissions via the EC2 API.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-33551, GHSA-4phw-6824-6cfp, PYSEC-2026-202

## What is CVE-2026-33551?

CVE-2026-33551 is a low-severity vulnerability in OpenStack Keystone, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-33551?

3 open source packages ship an affected version, including keystone. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keystone` | PyPI | From 14.0.0 | 26.1.1 |
| `keystone` | PyPI | From 14.0.0 | 26.1.1 |
| `keystone` | PyPI | From 14.0.0 | 26.1.1 |

Products: Openstack Keystone.

## How do I fix CVE-2026-33551?

Upgrade keystone to 26.1.1 or later.

## Is CVE-2026-33551 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33551 exists.

## Other vulnerabilities in OpenStack Keystone

- [CVE-2020-12690](https://insights.sbomify.com/CVE-2020-12690/): Insufficient Session Expiration in OpenStack Keystone (high 8.8)
- [CVE-2019-19687](https://insights.sbomify.com/CVE-2019-19687/): OpenStack Keystone Credential Leakage (high 8.8)
- [CVE-2026-43001](https://insights.sbomify.com/CVE-2026-43001/): OpenStack Keystone has an Incorrect Authorization Issue (high 7.9)
- [CVE-2014-2828](https://insights.sbomify.com/CVE-2014-2828/): OpenStack Identity (Keystone) DoS through V3 API authentication chaining (high 7.8)
- [CVE-2021-38155](https://insights.sbomify.com/CVE-2021-38155/): OpenStack Keystone allows information disclosure during account locking (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33551 and fix it if it is affected.

What it is: CVE-2026-33551 is a low-severity vulnerability in OpenStack Keystone, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33551 exists.

Affected packages and fixed versions:
- keystone (PyPI): affected from 14.0.0; fixed in 26.1.1
- keystone (PyPI): affected from 14.0.0; fixed in 26.1.1
- keystone (PyPI): affected from 14.0.0; fixed in 26.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33551/ (Markdown: https://insights.sbomify.com/CVE-2026-33551/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33551
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33551
- OSV: https://osv.dev/vulnerability/CVE-2026-33551

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33551/
Summaries are generated and may contain mistakes; the official description above is the record.