vulns.co
/
GKData.io MCP and API Buy me a coffee

OpenFGA

OpenFGA: policy intersections must preserve explicit exclusions

OpenFGA's maintainer advisory describes excluded users incorrectly returning in user-enumeration results (CVE-2026-61709). This happened with a particular combination of wildcard membership, exclusion and intersection, where another policy component could reintroduce a denied user. Combining permission sets must preserve explicit exclusions.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Editorial lesson: reason about policy results as complete sets, including exclusions, rather than merging positive membership alone. Design contained regression cases that compare composed policy outcomes with their intended semantics. The maintainer recommends OpenFGA 1.18.1 or later and lists Helm chart 0.3.10 as patched.

Before reading

  • Basic object-level authorization and policy-composition concepts

Context and limits

  • Applies when an application relies on ListUsers and its model combines a wildcard-based exclusion with an intersected relation that explicitly grants the excluded user. This does not establish that all models or authorization APIs are affected.
  • The advisory establishes an incorrect result; downstream unauthorized disclosure depends on application use. No production incident or independently verified impact is reported.
  • Published July 16, 2026 by justincoh; reporter 5ud0er is credited. Affected OpenFGA versions are listed through 1.18.0, Helm charts through 0.3.9. Patch release dates and resource-edition dates are not established.

Sources

  1. OpenFGA Improper Policy EnforcementOpenFGA · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software