OpenFGA: ListUsers returns a deliberately-excluded user when a `but not` exclusion under a type-bound wildcard is intersected (`and`) with another relation that also grants that user
Historical advisory saved 24 Oct 2026 13:19:41 UTC. The publisher may have updated it since then. Latest advisory.
osv · GHSA-g3pg-frfm-pr2m
Published### Description In OpenFGA, the ListUsers API could incorrectly return a user who should have been excluded. ### Preconditions This applies if all of the following are present: - 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 ### Fix Upgrade to OpenFGA v1.18.1 or greater. ### Acknowledgements OpenFGA would like to thank @5ud0er for the detailed report.
- Source published
- 16 Sep 2026 22:15:09 UTC
- Source modified
- 28 Sep 2026 17:11:12 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Publisher rating · MODERATE