CVE-2026-41131

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.

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.

### 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.

### 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.