# CVE-2026-80184: Auth bypass in Keystone

> Attackers can bypass project scope restrictions in OpenStack Keystone by reauthenticating delegated tokens, gaining unauthorized access to other projects.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80184, GHSA-x764-fvmq-4x2r, UBUNTU-CVE-2026-80184

## What is CVE-2026-80184?

CVE-2026-80184 is a high-severity authentication bypass vulnerability in OpenStack Keystone, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-80184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80184 is a high-severity authentication bypass vulnerability in OpenStack Keystone, published on 25 Aug 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-80184 exists.

Affected product: OpenStack Keystone. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-80184/ (Markdown: https://insights.sbomify.com/CVE-2026-80184/index.md)
```

## Sources

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

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