<?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 14:59:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-14778 — Keycloak: incorrect ownership checks in /uma-policy/</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-14778</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat build of Keycloak 26.2, Red Hat build of Keycloak 26.2.13, Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4.9&lt;/p&gt;
&lt;p&gt;A flaw was found in Keycloak. A significant Broken Access Control vulnerability exists in the UserManagedPermissionService (UMA Protection API). When updating or deleting a UMA policy associated with multiple resources, the authorization check only verifies the caller&amp;#39;s ownership against the first resource in the policy&amp;#39;s list. This allows a user (Owner A) who owns one resource (RA) to update a shared policy and modify authorization rules for other resources (e.g., RB) in that same policy, even if those other resources are owned by a different user (Owner B). This constitutes a horizontal privilege escalation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat build of Keycloak 26.2, Red Hat build of Keycloak 26.2.13, Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4.9&lt;/p&gt;
&lt;p&gt;A flaw was found in Keycloak. A significant Broken Access Control vulnerability exists in the UserManagedPermissionService (UMA Protection API). When updating or deleting a UMA policy associated with multiple resources, the authorization check only verifies the caller&amp;#39;s ownership against the first resource in the policy&amp;#39;s list. This allows a user (Owner A) who owns one resource (RA) to update a shared policy and modify authorization rules for other resources (e.g., RB) in that same policy, even if those other resources are owned by a different user (Owner B). This constitutes a horizontal privilege escalation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-14778</guid>
    </item>
  </channel>
</rss>
