CVE-2026-80183 OpenStack CVE debrief

Who should care

OpenStack Keystone administrators and users with role:reader permissions on any project should assess exposure and verify patch application. Affected operator, platform, vulnerability-management, and security-team impact should be reviewed to prioritize verifying and mitigating this vulnerability.

Why it matters

CVE-2026-80183 allows authenticated users to list project-scoped role assignments under any domain in OpenStack Keystone, potentially enabling an attacker to map role assignments across the cloud.

• An attacker can harvest domain IDs and map role assignments across the entire cloud.
• Role assignments can be enumerated without elevated privileges.
• User, group, project, and role names and home-domain IDs can be disclosed.

Technical summary

The vulnerability in OpenStack Keystone allows any authenticated user holding role:reader on any project to 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. This issue arises from the misuse of 'None' in the list_role_assignments_for_tree function, enabling an attacker to harvest domain IDs and map role assignments across the entire cloud. 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.

Defensive priority

Defenders should prioritize verifying and mitigating this vulnerability, especially in OpenStack Keystone deployments.

Recommended defensive actions

• Verify OpenStack Keystone version and apply patch 29.0.3 if vulnerable
• Restrict role assignments to necessary personnel
• Monitor role assignment queries for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability in OpenStack Keystone is caused by the misuse of 'None' in list_role_assignments_for_tree. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. This allows an attacker to harvest domain IDs and map role assignments across the entire cloud. To verify patch application, defenders should review the official advisory and confirm affected product deployments exist in managed environments. Evidence limits suggest verifying role assignment queries for suspicious activity

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.