All reports
Medium

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

Affected versions

Version ranges need review.

Affected versions
<1.18.1
Fixed version
1.18.1
Affected versions
<= 1.18.0
Fixed version
1.18.1
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-61709

Probability of exploitation in the next 30 days: 0.35%

FIRST EPSS · 2026-11-21

Description

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.

Links

Credits

  • 5ud0er