MediumGHSA-2hm9-h873-pgqhCVE-2023-43645GO-2023-2084

OpenFGA Vulnerable to DoS from circular relationship definitions

Published 28 Sept 2023 · Updated 10 Sept 2026

Is your project on an affected github.com/openfga/openfga?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.3.2
Fixed in
1.3.2
Update to the fixed version for your release line, for example:go get github.com/openfga/openfga@v1.3.2

Details

Overview

OpenFGA is vulnerable to a DoS attack when certain Check calls are executed against authorization models that contain circular relationship definitions. When the call is made, it's possible for the server to exhaust resources and die.

Am I Affected?

Yes, if your store contains an authorization model that allows circular relationships. For example, with this model:

model
  schema 1.1

type user

type group
  relations
    define memberA: [user] or memberB or memberC or memberD or memberE
    define memberB: [user] or memberA or memberC or memberD or memberE
    define memberC: [user] or memberA or memberB or memberD or memberE
    define memberD: [user] or memberA or memberB or memberC or memberE
    define memberE: [user] or memberA or memberB or memberC or memberD

This Check: (user:anne, memberA, group:X) can exhaust memory in the server.

Fix

Upgrade to v1.3.2 and update any offending models.

[BREAKING] If your model contained cycles or a relation definition that has the relation itself in its evaluation path, then Checks and queries that require evaluation will no longer be evaluated on v1.3.2+ and will return errors instead. You will need to update your models to remove the cycles.

Is GHSA-2hm9-h873-pgqh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/openfga/openfga, and gives you the command that fixes it.

More advisories for github.com/openfga/openfga

  • LowCVE-2026-61709OpenFGA: 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 in github.com/openfga/openfga · 28 Sept 2026
  • MediumCVE-2026-61709OpenFGA: 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 · 16 Sept 2026
  • LowCVE-2026-55689OpenFGA: OIDC audience validation skipped when --authn-oidc-audience is unset in github.com/openfga/openfga · 25 Jun 2026
  • LowCVE-2026-34972OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision in github.com/openfga/openfga · 25 Jun 2026
  • LowCVE-2026-55170OpenFGA Improper Policy Enforcement in github.com/openfga/openfga · 25 Jun 2026
  • LowCVE-2026-48096OpenFGA has cache-key delimiter injection in shared-iterator and v2 iterator that caches enables intra-store authorization-decision poisoning in github.com/openfga/openfga · 25 Jun 2026
All 53 advisories for github.com/openfga/openfga

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.