CVE-2025-48371: OpenFGA Authorization Bypass

Published May 22, 2025
·
Updated

Overview OpenFGA v1.8.0 to v1.8.12 ( openfga-0.2.16 <= Helm chart <= openfga-0.2.31, v1.8.0 <= docker <= v.1.8.12) are vulnerable to authorization bypass when certain Check and ListObject calls are executed.

Am I Affected? If you are using OpenFGA v1.8.0 to v1.8.12, specifically under the following conditions, you are affected by this authorization bypass vulnerability: - Calling Check API or ListObjects with an authorization model that has a relationship directly assignable by both type bound public access and userset, and - There are check or list object queries with contextual tuples for the relationship that can be directly assignable by both type bound public access and userset, and - Those contextual tuples’s user field is an userset, and - Type bound public access tuples are not assigned to the relationship

Fix Upgrade to v1.8.13. This upgrade is backwards compatible.

Acknowledgments Okta would like to thank @udyvish for discovering this vulnerability.

Other sources

OpenFGA is an authorization/permission engine. OpenFGA versions 1.8.0 through 1.8.12 (corresponding to Helm chart openfga-0.2.16 through openfga-0.2.30 and docker 1.8.0 through 1.8.12) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Users are affected under four specific conditions: First, calling Check API or ListObjects with an authorization model that has a relationship directly assignable by both type bound public access and userset; second, there are check or list object queries with contextual tuples for the relationship that can be directly assignable by both type bound public access and userset; third, those contextual tuples’s user field is an userset; and finally, type bound public access tuples are not assigned to the relationship. Users should upgrade to version 1.8.13 to receive a patch. The upgrade is backwards compatible.

NVD

Affected Software

4 affected componentsFixes available
OPenFGA OPenFGA>=1.8.0<=1.8.12
go/github.com/openfga/openfga>=1.8.0<1.8.13
1.8.13
OPenFGA Helm Charts Openfga>=0.2.16<0.2.32
OPenFGA OPenFGA>=1.8.0<1.8.13

Event History

May 22, 2025
CVE Published
via MITRE·10:20 PM
Data Sourced
via MITRE·10:20 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyAffected Software
May 23, 2025
Advisory Published
via GitHub·06:41 PM
Data Sourced
via GitHub·06:41 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-48371?

CVE-2025-48371 has a high severity due to its potential for unauthorized access through authorization bypass.

2

How do I fix CVE-2025-48371?

To fix CVE-2025-48371, upgrade OpenFGA from any affected version (1.8.0 through 1.8.12) to a secure version beyond 1.8.12.

3

What products are affected by CVE-2025-48371?

CVE-2025-48371 affects OpenFGA versions from 1.8.0 to 1.8.12, including corresponding Helm charts and Docker images.

4

What types of calls are involved in CVE-2025-48371?

CVE-2025-48371 involves an authorization bypass during certain Check and ListObject API calls.

5

Is there a known exploit for CVE-2025-48371?

Yes, CVE-2025-48371 allows attackers to exploit the authorization bypass to gain unauthorized access to protected resources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203