OpenFGA Authorization Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.8 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H · score source

EPSS

• CVE-2025-46331: 0.40% estimated exploitation activity in the next 30 days; percentile 33.79 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Overview OpenFGA v1.8.10 or previous (Helm chart <= openfga-0.2.28, docker <= v.1.8.10) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Am I Affected? If you are using OpenFGA v1.8.10 or previous, specifically under the following conditions, you are affected by this authorization bypass vulnerability: - Calling Check API or ListObjects with an authorization model that has tuple cycle. - Check query cache is enabled, and - There are multiple check / list objects requests involving the tuple cycle within the check query TTL Fix Upgrade to v1.8.11. This upgrade is backwards compatible.

Published by the source

30 Apr 2025, 16:43 UTC

Last modified by the source

1 May 2025, 13:30 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w222-m46c-mgh6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-46331

Advisory: OpenFGA Authorization Bypass
IDs: CVE-2025-46331, GHSA-w222-m46c-mgh6
Record: https://patchnext.com/advisories/cve-2025-46331 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openfga/openfga 1.8.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openfga/openfga: affected >= 1.3.6, < 1.8.11; fixed in 1.8.11

## Suggested inspection (read-only)
- Go github.com/openfga/openfga: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openfga/openfga.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w222-m46c-mgh6 (GitHub-reviewed advisory GHSA-w222-m46c-mgh6 lists affected ranges: Go github.com/openfga/openfga >=1.3.6 <1.8.11)

Commands are suggestions: review each one before running it.