<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 12:36:33 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-340501</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-340501</link>
      <description>EUVD-2026-340501</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-340501</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43000</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43000</link>
      <description>&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43000</guid>
    </item>
    <item>
      <title>GHSA-q623-f4j4-p4xj — OpenStack Keystone has an Incorrect Authorization issue</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q623-f4j4-p4xj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keystone&lt;/p&gt;
&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keystone&lt;/p&gt;
&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q623-f4j4-p4xj</guid>
    </item>
    <item>
      <title>PYSEC-2026-601</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-601</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keystone&lt;/p&gt;
&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keystone&lt;/p&gt;
&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-601</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43000</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43000</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:25.10: keystone, Ubuntu:26.04:LTS: keystone&lt;/p&gt;
&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&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:25.10: keystone, Ubuntu:26.04:LTS: keystone&lt;/p&gt;
&lt;p&gt;An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim&amp;#39;s identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim&amp;#39;s actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim&amp;#39;s admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim&amp;#39;s identity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43000</guid>
    </item>
  </channel>
</rss>
