Cross-domain role disclosure via null scope comparison
Published Aug 26, 2026 · Updated Aug 27, 2026
Type confusion in affected OpenStack Keystone releases before 29.0.3 allows remote authenticated users to disclose cross-domain role assignments. list_role_assignments_for_tree treats a domain project whose domain_id is null as matching the caller's project-domain policy target. A reader role on any project and a domain ID are sufficient; include_names exposes the involved users, groups, projects, roles, and home-domain IDs.
Summary
What happened
Type confusion in affected OpenStack Keystone releases before 29.0.3 allows remote authenticated users to disclose cross-domain role assignments. list_role_assignments_for_tree treats a domain project whose domain_id is null as matching the caller's project-domain policy target. A reader role on any project and a domain ID are sufficient; include_names exposes the involved users, groups, projects, roles, and home-domain IDs.
The record
- CVE
- CVE-2026-80183
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- Vendor
- OpenStack
- Product
- Keystone
- Classifications
- CWE-843, T1087.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.0.0 <27.0.3
- Affected versionversion=28.0.0 <28.0.3
- Affected versionversion=29.0.0 <29.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo