OpenFGA has an Authorization Bypass through cached keys
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.8epss 0.2%
exploitation probability
0.2%top 85% of all CVEs
observed exploitation
nono source reports it
In short
OpenFGA's caching system can incorrectly reuse cached authorization results for different requests when conditions are involved, allowing an attacker to bypass access controls by triggering the same cache key for a different user or permission check.
Technical detail
In OpenFGA versions before 1.13.1, models using condition evaluation with caching enabled generate identical cache keys for distinct authorization requests, leading to authorization bypass. The vulnerability requires conditions to be present in relations and caching to be active; an attacker exploits this by crafting requests that collide with cached results from prior checks with different authorization contexts.
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. 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.
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
Affected products
openfga · openfga