<?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>Tue, 29 Sep 2026 09:18:31 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-61709</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-61709</link>
      <description>&lt;p&gt;OpenFGA is an authorization and permission engine built for developers. Prior to 1.18.1, the ListUsers API could return a user that should have been excluded when an authorization relation used an intersection containing a base but not excluded operand, the base was granted through a type-bound public wildcard, and the excluded user also had a concrete tuple through another intersection operand. In pkg/server/commands/listusers/list_users_rpc.go, expandIntersection counted the concrete tuple and wildcard without first rejecting entries in excludedUsersMap. Applications that used ListUsers to enumerate or enforce access could therefore treat an excluded user as authorized. This issue is fixed in version 1.18.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenFGA is an authorization and permission engine built for developers. Prior to 1.18.1, the ListUsers API could return a user that should have been excluded when an authorization relation used an intersection containing a base but not excluded operand, the base was granted through a type-bound public wildcard, and the excluded user also had a concrete tuple through another intersection operand. In pkg/server/commands/listusers/list_users_rpc.go, expandIntersection counted the concrete tuple and wildcard without first rejecting entries in excludedUsersMap. Applications that used ListUsers to enumerate or enforce access could therefore treat an excluded user as authorized. This issue is fixed in version 1.18.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-61709</guid>
    </item>
    <item>
      <title>GHSA-g3pg-frfm-pr2m — OpenFGA: ListUsers returns a deliberately-excluded user when a `but not` exclusion under a type-bound wildcard is inter…</title>
      <link>https://db.gcve.eu/vuln/ghsa-g3pg-frfm-pr2m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openfga/openfga&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;In OpenFGA, the ListUsers API could incorrectly return a user who should have been excluded.&lt;/p&gt;
&lt;p&gt;### Preconditions&lt;/p&gt;
&lt;p&gt;This applies if all of the following are present:&lt;/p&gt;
&lt;p&gt;- The authorization model contains a relation defined as an intersection (and) where at least one operand is an exclusion of the form base but not excluded: e.g. `rel1: (public_user but not blocked) and rel2`
- The base side of that exclusion is granted through a type-bound public wildcard (e.g. user:*).
- A user excluded by the but not clause is also granted, via a concrete tuple, through another operand of the intersection.
- Your application uses ListUsers to enumerate or enforce access&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;Upgrade to OpenFGA v1.18.1 or greater.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;OpenFGA would like to thank @5ud0er for the detailed report.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/openfga/openfga&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;In OpenFGA, the ListUsers API could incorrectly return a user who should have been excluded.&lt;/p&gt;
&lt;p&gt;### Preconditions&lt;/p&gt;
&lt;p&gt;This applies if all of the following are present:&lt;/p&gt;
&lt;p&gt;- The authorization model contains a relation defined as an intersection (and) where at least one operand is an exclusion of the form base but not excluded: e.g. `rel1: (public_user but not blocked) and rel2`
- The base side of that exclusion is granted through a type-bound public wildcard (e.g. user:*).
- A user excluded by the but not clause is also granted, via a concrete tuple, through another operand of the intersection.
- Your application uses ListUsers to enumerate or enforce access&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;Upgrade to OpenFGA v1.18.1 or greater.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;OpenFGA would like to thank @5ud0er for the detailed report.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g3pg-frfm-pr2m</guid>
    </item>
    <item>
      <title>RHSA-2026:67605 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2026:67605</link>
      <description>&lt;p&gt;grafana: Grafana: Arbitrary code execution and information disclosure via Cross-Site Scripting in geomap panel grafana: tempo: loki: Tempo and Loki Datasource Plugins: Information disclosure and unauthorized actions via path traversal github.com/openfga/openfga: OpenFGA: Unauthorized access due to ListUsers API returning deliberately excluded users. joi: joi: Prototype Pollution via custom messages&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;grafana: Grafana: Arbitrary code execution and information disclosure via Cross-Site Scripting in geomap panel grafana: tempo: loki: Tempo and Loki Datasource Plugins: Information disclosure and unauthorized actions via path traversal github.com/openfga/openfga: OpenFGA: Unauthorized access due to ListUsers API returning deliberately excluded users. joi: joi: Prototype Pollution via custom messages&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2026:67605</guid>
    </item>
  </channel>
</rss>
