CVE-2026-41131: OpenFGA has Improper Policy Enforcement
Description In OpenFGA, in specific scenarios, models using conditions with caching enabled can result in two different check requests producing the same cache key. This could result in OpenFGA reusing an earlier cached result for a subsequent request.
Am I Affected? Users are affected if their applications meet the following preconditions:
The model has relations which rely on condition evaluation. Caching is enabled.
Fix Upgrade to OpenFGA v1.14.1.
Acknowledgement OpenFGA would like to thank @bugbunny-research for the detailed report.
Other sources
OpenFGA is an authorization/permission engine built for developers. Prior to version 1.14.1, in specific scenarios, models using conditions with caching enabled can result in two different check requests producing the same cache key. This could result in OpenFGA reusing an earlier cached result for a subsequent request. The preconditions for vulnerability are the model having relations which rely on condition evaluation and the user having caching enabled. OpenFGA v1.14.1 contains a fix.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41131?
CVE-2026-41131 is classified as a high severity vulnerability due to its potential to compromise authorization checks.
How do I fix CVE-2026-41131?
To fix CVE-2026-41131, upgrade OpenFGA to version 1.14.1 or later.
What systems are affected by CVE-2026-41131?
CVE-2026-41131 affects OpenFGA versions prior to 1.14.1.
What is the main issue described in CVE-2026-41131?
CVE-2026-41131 describes improper policy enforcement due to caching which can lead to incorrect authorization checks.
Is there a workaround for CVE-2026-41131?
There are no official workarounds for CVE-2026-41131; upgrading to the fixed version is recommended.