CVE-2025-25196
OpenFGA Authorization Bypass
In short
OpenFGA, an authorization system, has a flaw where it may incorrectly grant access to users in certain configurations combining public access and user group permissions. This could let unauthorized users perform actions they shouldn't be able to.
Technical detail
Authorization bypass in OpenFGA v1.8.4 and earlier occurs when Check or ListObjects APIs are called with models containing relations assignable to both public access and usersets of the same type, combined with type-bound public access tuples absent corresponding userset tuples. The vulnerability is triggered when the Check request's user field matches the type of the public access tuple's user type, resulting in incorrect permission evaluation.
Summary generated and translated by AI from the official description.
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.
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