<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 Oct 2026 07:45:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80183</title>
      <link>https://db.gcve.eu/vuln/cve-2026-80183</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenStack Keystone&lt;/p&gt;
&lt;p&gt;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&amp;#39;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 &amp;#34;default&amp;#34; 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 &amp;#34;None&amp;#34; in&lt;/p&gt;
&lt;p&gt;list_role_assignments_for_tree.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenStack Keystone&lt;/p&gt;
&lt;p&gt;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&amp;#39;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 &amp;#34;default&amp;#34; 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 &amp;#34;None&amp;#34; in&lt;/p&gt;
&lt;p&gt;list_role_assignments_for_tree.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-80183</guid>
    </item>
    <item>
      <title>USN-8854-1 — keystone vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8854-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: keystone, Ubuntu:Pro:18.04:LTS: keystone, Ubuntu:Pro:20.04:LTS: keystone, Ubuntu:22.04:LTS: keystone, Ubuntu:24.04:LTS: keystone, Ubuntu:26.04:LTS: keystone&lt;/p&gt;
&lt;p&gt;Grzegorz Grasza discovered that OpenStack Keystone did not consistently
enforce restrictions for delegated authentication tokens. An authenticated
attacker could possibly use this issue to create credentials or delegations
 that outlasted the delegated token. (CVE-2026-80182)&lt;/p&gt;
&lt;p&gt;It was discovered that OpenStack Keystone incorrectly handled role
assignment queries under certain circumstances. An authenticated attacker
could possibly use this issue to obtain sensitive information. This
issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04
LTS, and Ubuntu 26.04 LTS. (CVE-2026-80183)&lt;/p&gt;
&lt;p&gt;Tim Shephard discovered that OpenStack Keystone did not properly
restrict reauthentication using delegated tokens. An authenticated
attacker could possibly use this issue to escape their intended
project scope and obtain unauthorized access. (CVE-2026-80184)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: keystone, Ubuntu:Pro:18.04:LTS: keystone, Ubuntu:Pro:20.04:LTS: keystone, Ubuntu:22.04:LTS: keystone, Ubuntu:24.04:LTS: keystone, Ubuntu:26.04:LTS: keystone&lt;/p&gt;
&lt;p&gt;Grzegorz Grasza discovered that OpenStack Keystone did not consistently
enforce restrictions for delegated authentication tokens. An authenticated
attacker could possibly use this issue to create credentials or delegations
 that outlasted the delegated token. (CVE-2026-80182)&lt;/p&gt;
&lt;p&gt;It was discovered that OpenStack Keystone incorrectly handled role
assignment queries under certain circumstances. An authenticated attacker
could possibly use this issue to obtain sensitive information. This
issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04
LTS, and Ubuntu 26.04 LTS. (CVE-2026-80183)&lt;/p&gt;
&lt;p&gt;Tim Shephard discovered that OpenStack Keystone did not properly
restrict reauthentication using delegated tokens. An authenticated
attacker could possibly use this issue to escape their intended
project scope and obtain unauthorized access. (CVE-2026-80184)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8854-1</guid>
    </item>
  </channel>
</rss>
