<?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>Thu, 08 Oct 2026 16:49:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-56246 — Capgo - Cross-Organization Authorization Bypass via Scoped API Key Privilege Inheritance</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-56246</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Capgo&lt;/p&gt;
&lt;p&gt;Capgo before 12.128.2 contains a broken access control vulnerability in the organization management API where a scoped API key (limited_to_orgs) inherits its owner-user&amp;#39;s permissions, allowing destructive cross-organization actions. When a user is an admin in two organizations and creates a write-mode API key restricted to one organization, that key can still perform destructive operations (e.g., DELETE /organization, DELETE /organization/members) against another organization. The root cause is route-level authorization (rbac_check_permission_direct) that evaluates the key owner&amp;#39;s user privileges before enforcing the API key&amp;#39;s limited_to_orgs scope.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Capgo&lt;/p&gt;
&lt;p&gt;Capgo before 12.128.2 contains a broken access control vulnerability in the organization management API where a scoped API key (limited_to_orgs) inherits its owner-user&amp;#39;s permissions, allowing destructive cross-organization actions. When a user is an admin in two organizations and creates a write-mode API key restricted to one organization, that key can still perform destructive operations (e.g., DELETE /organization, DELETE /organization/members) against another organization. The root cause is route-level authorization (rbac_check_permission_direct) that evaluates the key owner&amp;#39;s user privileges before enforcing the API key&amp;#39;s limited_to_orgs scope.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-56246</guid>
    </item>
  </channel>
</rss>
