CVE-2026-33729: OpenFGA has an Authorization Bypass through cached keys
Description In OpenFGA, under specific conditions, models using conditions with caching enabled can result in two different check requests producing the same cache key. This can result in OpenFGA reusing an earlier cached result for a different request.
Am I Affected? Users are affected if the following preconditions are met: 1. The model has relations which rely on condition evaluation. 1. Caching is enabled.
Fix Upgrade to OpenFGA v1.13.1.
Acknowledgement OpenFGA would like to thank @Amemoyoi for the discovery and responsible disclosure.
Other sources
OpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. In versions prior to 1.13.1, under specific conditions, models using conditions with caching enabled can result in two different check requests producing the same cache key. This can result in OpenFGA reusing an earlier cached result for a different request. Users are affected if the model has relations which rely on condition evaluation andncaching is enabled. OpenFGA v1.13.1 contains a patch.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33729?
CVE-2026-33729 has a medium severity rating due to its potential to allow authorization bypass.
How do I fix CVE-2026-33729?
To mitigate CVE-2026-33729, upgrade to version 1.13.1 or later of OpenFGA.
What systems are affected by CVE-2026-33729?
CVE-2026-33729 affects OpenFGA versions prior to 1.13.1 that utilize caching strategies in authorization models.
What type of vulnerability is CVE-2026-33729?
CVE-2026-33729 is classified as an authorization bypass vulnerability.
Can CVE-2026-33729 affect data security?
Yes, CVE-2026-33729 can potentially compromise data security by allowing unauthorized access to certain resources.