OpenFGA Authorization Bypass
cve-program · CVE-2025-25196
PublishedOpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. OpenFGA < v1.8.4 (Helm chart < openfga-0.2.22, docker < v.1.8.4) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Users on OpenFGA v1.8.4 or previous, specifically under the following conditions are affected by this authorization bypass vulnerability: 1. Calling Check API or ListObjects with a model that has a relation directly assignable to both public access AND userset with the same type. 2. A type bound public access tuple is assigned to an object. 3. userset tuple is not assigned to the same object. and 4. Check request's user field is a userset that has the same type as the type bound public access tuple's user type. Users are advised to upgrade to v1.8.5 which is backwards compatible. There are no known workarounds for this vulnerability.
Read the publisher's advisoryeuvd · EUVD-2025-4651
PublishedOpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. OpenFGA < v1.8.4 (Helm chart < openfga-0.2.22, docker < v.1.8.4) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Users on OpenFGA v1.8.4 or previous, specifically under the following conditions are affected by this authorization bypass vulnerability: 1. Calling Check API or ListObjects with a model that has a relation directly assignable to both public access AND userset with the same type. 2. A type bound public access tuple is assigned to an object. 3. userset tuple is not assigned to the same object. and 4. Check request's user field is a userset that has the same type as the type bound public access tuple's user type. Users are advised to upgrade to v1.8.5 which is backwards compatible. There are no known workarounds for this vulnerability.
Read the publisher's advisorynvd · CVE-2025-25196
PublishedOpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. OpenFGA < v1.8.4 (Helm chart < openfga-0.2.22, docker < v.1.8.4) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Users on OpenFGA v1.8.4 or previous, specifically under the following conditions are affected by this authorization bypass vulnerability: 1. Calling Check API or ListObjects with a model that has a relation directly assignable to both public access AND userset with the same type. 2. A type bound public access tuple is assigned to an object. 3. userset tuple is not assigned to the same object. and 4. Check request's user field is a userset that has the same type as the type bound public access tuple's user type. Users are advised to upgrade to v1.8.5 which is backwards compatible. There are no known workarounds for this vulnerability.
Read the publisher's advisoryosv · GHSA-g4v5-6f5p-m38j
PublishedOverview OpenFGA v1.8.4 or previous (Helm chart < openfga-0.2.22, docker < v.1.8.5) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Am I Affected? If you are using OpenFGA v1.8.4 or previous, specifically under the following conditions, you are affected by this authorization bypass vulnerability: - Calling Check API or ListObjects with a model that has a relation [directly assignable](https://openfga.dev/docs/concepts#what-is-a-directly-related-user-type) to both [public access](https://openfga.dev/docs/concepts#what-is-type-bound-public-access) AND [userset](https://openfga.dev/docs/concepts#what-is-a-user) with the [same type](https://openfga.dev/docs/concepts#what-is-a-type), and - A type bound public access tuple is assigned to an object, and - userset tuple is not assigned to the same object, and - Check request's user field is a userset that has the same type as the type bound public access tuple's user type Fix Upgrade to v1.8.5. This upgrade is backwards compatible.
Read the publisher's advisoryosv · GO-2025-3470
PublishedOpenFGA Authorization Bypass in github.com/openfga/openfga
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-25196 · CVE overview and exploitation status
cve-program · CVE-2025-25196
- https://github.com/openfga/openfga/security/advisories/GHSA-g4v5-6f5p-m38j
- https://github.com/openfga/openfga/commit/0aee4f47e0c642de78831ceb27bb62b116f49588
euvd · EUVD-2025-4651
- https://github.com/openfga/openfga/security/advisories/GHSA-g4v5-6f5p-m38j
- https://github.com/openfga/openfga/commit/0aee4f47e0c642de78831ceb27bb62b116f49588
nvd · CVE-2025-25196
- https://github.com/openfga/openfga/commit/0aee4f47e0c642de78831ceb27bb62b116f49588
- https://github.com/openfga/openfga/security/advisories/GHSA-g4v5-6f5p-m38j
osv · GHSA-g4v5-6f5p-m38j
- https://github.com/openfga/openfga/security/advisories/GHSA-g4v5-6f5p-m38j
- https://nvd.nist.gov/vuln/detail/CVE-2025-25196
- https://github.com/openfga/openfga/commit/0aee4f47e0c642de78831ceb27bb62b116f49588
- https://github.com/openfga/openfga
osv · GO-2025-3470
Related changes
Linked by CVE identifierNo related changes are available here.