# CVE-2026-80183: Information disclosure in Keystone

> Authenticated users can list all project-scoped role assignments across domains, exposing sensitive user, group, and project metadata.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/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:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80183, GHSA-xmh6-7768-658c, UBUNTU-CVE-2026-80183

## What is CVE-2026-80183?

CVE-2026-80183 is a high-severity vulnerability in OpenStack Keystone, published on 26 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, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain ID as scope.project.id with include_subtree to the GET /v3/role_assignments endpoint. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. With include_names, the response discloses the names and home-domain IDs of every user, group, project, and role involved. The literal "default" domain ID works against any deployment created with keystone-manage bootstrap. An attacker can harvest domain IDs from the response and repeat the query to map role assignments across the entire cloud. This is caused by misuse of "None" in 

list_role_assignments_for_tree.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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


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

Upgrade to a fixed version.

## Is CVE-2026-80183 being exploited?

There is no known exploitation of CVE-2026-80183 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80183 is a high-severity vulnerability in OpenStack Keystone, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80183 in the wild and no public exploit code.

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

## Sources

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

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