CVE-2025-25196
OpenFGA Authorization Bypass
OpenFGA 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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
5.8
OpenFGA Authorization Bypass
OpenFGA 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.
- Record
CVE-2025-25196- CVSS 4.0
- 5.8 Medium
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 - Weakness
- CWE-285
- Updated
- 2026-11-02
EUVDEUVD-2025-4651
5.8
OpenFGA 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.
- Record
EUVD-2025-4651- CVSS 4.0
- 5.8 Medium
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 - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-g4v5-6f5p-m38j
5.8
OpenFGA Authorization Bypass
Overview 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 to both public access AND userset with the same 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.
- Record
GHSA-g4v5-6f5p-m38j- CVSS 4.0
- 5.8 Medium
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 - Weakness
- CWE-285
- Updated
- 2026-11-02
NVD
5.8
OpenFGA 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.
- Record
CVE-2025-25196- CVSS 4.0
- 5.8 Medium
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-285
- Updated
- 2026-11-02
OSV
5.8
OpenFGA Authorization Bypass
OpenFGA 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.
- Record
CVE-2025-25196- CVSS 4.0
- 5.8 Medium
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 - Weakness
- CWE-285
- Updated
- 2026-11-02
OSVGHSA-g4v5-6f5p-m38j
5.8
OpenFGA Authorization Bypass
Overview 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 to both public access AND userset with the same 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.
- Record
GHSA-g4v5-6f5p-m38j- CVSS 4.0
- 5.8 Medium
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 - Weakness
- CWE-285
- Updated
- 2026-11-02
OSVGO-2025-3470 No score
OpenFGA Authorization Bypass in github.com/openfga/openfga
OpenFGA Authorization Bypass in github.com/openfga/openfga
- Record
GO-2025-3470- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:14889-1 No score
govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media
These are all security issues fixed in the govulncheck-vulndb-0.0.20250312T181707-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:14889-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/openfga/openfgaGo |
through 1.8.4 | 1.8.5 |
github.com/openfga/openfgaGo |
before 1.8.5 | 1.8.5 |
govulncheck-vulndbopenSUSE:Tumbleweed From an advisory covering 31 CVEs |
before 0.0.20250312T181707-1.1 | 0.0.20250312T181707-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-25196 is a medium vulnerability (CVSS 5.8) in Openfga, published February 19, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.43%, the 37th percentile. Fixed in github.com/openfga/openfga 1.8.5.
References
github.com/openfga/openfga/security/advisories/GHSA-g4v5-6f5p-m38j
github.com/openfga/openfga/commit/0aee4f47e0c642de78831ceb27bb62b116f49588
nvd.nist.gov/vuln/detail/CVE-2025-25196
github.com/advisories/GHSA-g4v5-6f5p-m38j
github.com/CVEProject/cvelistV5/tree/main/cves/2025/25xxx/CVE-2025-25196.json
github.com/openfga/openfga
Show 31 moreShow less
suse.com/security/cve/CVE-2024-57603
suse.com/security/cve/CVE-2024-57604
suse.com/security/cve/CVE-2025-0426
suse.com/security/cve/CVE-2025-1243
suse.com/security/cve/CVE-2025-1293
suse.com/security/cve/CVE-2025-1412
suse.com/security/cve/CVE-2025-20051
suse.com/security/cve/CVE-2025-22870
suse.com/security/cve/CVE-2025-22952
suse.com/security/cve/CVE-2025-23387
suse.com/security/cve/CVE-2025-23388
suse.com/security/cve/CVE-2025-23389
suse.com/security/cve/CVE-2025-24016
suse.com/security/cve/CVE-2025-24526
suse.com/security/cve/CVE-2025-24806
suse.com/security/cve/CVE-2025-24976
suse.com/security/cve/CVE-2025-25196
suse.com/security/cve/CVE-2025-25199
suse.com/security/cve/CVE-2025-25204
suse.com/security/cve/CVE-2025-25279
suse.com/security/cve/CVE-2025-25294
suse.com/security/cve/CVE-2025-27088
suse.com/security/cve/CVE-2025-27090
suse.com/security/cve/CVE-2025-27100
suse.com/security/cve/CVE-2025-27112
suse.com/security/cve/CVE-2025-27144
suse.com/security/cve/CVE-2025-27155
suse.com/security/cve/CVE-2025-27414
suse.com/security/cve/CVE-2025-27421
suse.com/security/cve/CVE-2025-27507
suse.com/security/cve/CVE-2025-27509