Access of Resource Using Incompatible Type ('Type Confusion') Affecting keystone package, versions <2:29.0.2-2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-KEYSTONE-19342035
- published27 Aug 2026
- disclosed27 Aug 2026
Introduced: 27 Aug 2026
NewCVE-2026-80183 (opens in a new tab)How to fix?
Upgrade Debian:unstable keystone to version 2:29.0.2-2 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream keystone package and not the keystone package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
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.