<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T09:18:31.336049+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-61709</id>
    <title>fkie_cve-2026-61709</title>
    <updated>2026-09-29T09:18:31.423857+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-61709"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-g3pg-frfm-pr2m</id>
    <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>
    <updated>2026-09-29T09:18:31.423938+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/openfga/openfga</p>
<p>### Description</p>
<p>In OpenFGA, the ListUsers API could incorrectly return a user who should have been excluded.</p>
<p>### Preconditions</p>
<p>This applies if all of the following are present:</p>
<p>- 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</p>
<p>### Fix</p>
<p>Upgrade to OpenFGA v1.18.1 or greater.</p>
<p>### Acknowledgements</p>
<p>OpenFGA would like to thank @5ud0er for the detailed report.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-g3pg-frfm-pr2m"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/rhsa-2026:67605</id>
    <title>RHSA-2026:67605 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
    <updated>2026-09-29T09:18:31.423986+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/rhsa-2026:67605"/>
  </entry>
</feed>
