<?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>Sat, 07 Nov 2026 02:31:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-96547 — Keycloak-services: keycloak-services: dcr registration-time claim-path gap allows forging realm_access.roles</title>
      <link>https://db.gcve.eu/vuln/cve-2026-96547</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4.17, Red Hat build of Keycloak 26.6, Red Hat build of Keycloak 26.6.8, Red Hat Single Sign-On 7&lt;/p&gt;
&lt;p&gt;A flaw was found in the Dynamic Client Registration component of Keycloak, an open-source identity and access management solution. The issue occurs because the system does not properly restrict which claim names can be used when setting up new clients. An attacker with valid registration credentials could create a client that incorrectly maps standard user profile information to sensitive security roles, potentially allowing them to gain unauthorized privileges on external applications that trust Keycloak tokens.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4.17, Red Hat build of Keycloak 26.6, Red Hat build of Keycloak 26.6.8, Red Hat Single Sign-On 7&lt;/p&gt;
&lt;p&gt;A flaw was found in the Dynamic Client Registration component of Keycloak, an open-source identity and access management solution. The issue occurs because the system does not properly restrict which claim names can be used when setting up new clients. An attacker with valid registration credentials could create a client that incorrectly maps standard user profile information to sensitive security roles, potentially allowing them to gain unauthorized privileges on external applications that trust Keycloak tokens.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-96547</guid>
    </item>
  </channel>
</rss>
