<?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>Sun, 22 Nov 2026 21:45:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63505 — Probo: Cross-tenant IDOR via unvalidated FK references</title>
      <link>https://db.gcve.eu/vuln/cve-2026-63505</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getprobo probo&lt;/p&gt;
&lt;p&gt;Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Prior to version 0.223.1, Probo&amp;#39;s console GraphQL API is a multi-tenant GRC platform where all data is scoped to an organization. A Finding can reference a Risk via finding.riskId. That reference is stored without validating that the risk belongs to the caller&amp;#39;s organization, and the Finding.risk field resolver authorizes the finding (caller&amp;#39;s org) instead of the risk, then loads the risk with a tenant scope derived from the risk&amp;#39;s own global ID. As a result, an authenticated member of organization A can attach an arbitrary organization B risk GID to a finding they own and then read organization B&amp;#39;s Risk (name, description, treatment, category, severity, owner) — with no membership in B. The stored cross-tenant reference also blocks B from deleting its own risk (ON DELETE RESTRICT), a cross-tenant integrity/DoS. This issue has been patched in version 0.223.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getprobo probo&lt;/p&gt;
&lt;p&gt;Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Prior to version 0.223.1, Probo&amp;#39;s console GraphQL API is a multi-tenant GRC platform where all data is scoped to an organization. A Finding can reference a Risk via finding.riskId. That reference is stored without validating that the risk belongs to the caller&amp;#39;s organization, and the Finding.risk field resolver authorizes the finding (caller&amp;#39;s org) instead of the risk, then loads the risk with a tenant scope derived from the risk&amp;#39;s own global ID. As a result, an authenticated member of organization A can attach an arbitrary organization B risk GID to a finding they own and then read organization B&amp;#39;s Risk (name, description, treatment, category, severity, owner) — with no membership in B. The stored cross-tenant reference also blocks B from deleting its own risk (ON DELETE RESTRICT), a cross-tenant integrity/DoS. This issue has been patched in version 0.223.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-63505</guid>
    </item>
  </channel>
</rss>
