# CVE-2023-35933: OpenFGA denial of service die to circular relationship

> Attackers can cause denial of service in OpenFGA by triggering circular relationship definitions in authorization models during Check or ListObjects calls.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2023
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-hr9r-8phq-5x8j, GO-2023-1872

## What is CVE-2023-35933?

CVE-2023-35933 is a medium-severity denial of service vulnerability in openfga, published on 26 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OPenFGA is an open source authorization/permission engine built for developers. OpenFGA versions v1.1.0 and prior are vulnerable to a DoS attack when Check and ListObjects calls are executed against authorization models that contain circular relationship definitions. Users are affected by this vulnerability if they are using OpenFGA v1.1.0 or earlier, and if you are executing `Check` or `ListObjects` calls against a vulnerable authorization model. Users are advised to upgrade to version 1.1.1. There are no known workarounds for this vulnerability. Users that do not have circular relationships in their models are not affected.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2023-35933?

3 open source packages ship an affected version, including github.com/openfga/openfga. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openfga/openfga` | Go | All versions | 1.1.1 |
| `github.com/openfga/openfga` | Go | All versions | 1.1.1 |
| `github.com/openfga/openfga` | Go | All versions | 1.1.1 |

Products: Openfga Openfga.

## How do I fix CVE-2023-35933?

Upgrade github.com/openfga/openfga to 1.1.1 or later.

## Is CVE-2023-35933 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35933 exists.

## Other vulnerabilities in openfga

- [CVE-2024-31452](https://insights.sbomify.com/CVE-2024-31452/): OpenFGA Authorization Bypass (high 8.1)
- [CVE-2022-23542](https://insights.sbomify.com/CVE-2022-23542/): OpenFGA Authorization Bypass (high 7.7)
- [CVE-2024-42473](https://insights.sbomify.com/CVE-2024-42473/): OpenFGA Authorization Bypass (high 7.5)
- [CVE-2026-40293](https://insights.sbomify.com/CVE-2026-40293/): OpenFGA Playground Preshared Key Exposure (medium 6.5)
- [CVE-2023-40579](https://insights.sbomify.com/CVE-2023-40579/): OpenFGA Authorization Bypass (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35933 and fix it if it is affected.

What it is: CVE-2023-35933 is a medium-severity denial of service vulnerability in openfga, published on 26 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35933 exists.

Affected packages and fixed versions:
- github.com/openfga/openfga (Go): affected all versions; fixed in 1.1.1
- github.com/openfga/openfga (Go): affected all versions; fixed in 1.1.1
- github.com/openfga/openfga (Go): affected all versions; fixed in 1.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-35933/ (Markdown: https://insights.sbomify.com/CVE-2023-35933/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-35933
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-35933
- OSV: https://osv.dev/vulnerability/CVE-2023-35933

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-35933/
Summaries are generated and may contain mistakes; the official description above is the record.