CVE-2026-34972: OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision
Description
In OpenFGA, under specific conditions, BatchCheck calls with multiple checks sent for the same object, relation, and user combination can result in improper policy enforcement.
Am I affected?
You are affected if you meet the following preconditions: 1. You execute BatchCheck operations which rely on context. 2. Multiple checks are sent within a single BatchCheck operation for the same user/object/relation combination, each containing context. 3. The contexts between those checks differ in a specific way
Fix Upgrade to OpenFGA v1.14.0
Acknowledgement OpenFGA would like to thank @bugbunny-research for the discovery and detailed report.
Other sources
OpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. From 1.8.0 to 1.13.1, under specific conditions, BatchCheck calls with multiple checks sent for the same object, relation, and user combination can result in improper policy enforcement. This vulnerability is fixed in 1.14.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/openfga/openfgato a version that resolves this vulnerability.Fixed in 1.14.0 - Upgrade
Upgrade
OpenFGAto a version that resolves this vulnerability.Fixed in 1.14.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-34972?
CVE-2026-34972 is classified as a high severity vulnerability due to incorrect authorization decisions that can lead to unauthorized access.
How do I fix CVE-2026-34972?
To fix CVE-2026-34972, upgrade OpenFGA to version 1.14.0 or later, or use the appropriate Helm chart version above 0.2.62.
What versions of OpenFGA are affected by CVE-2026-34972?
Versions of OpenFGA from 1.8.0 to 1.13.1 are affected by CVE-2026-34972.
What type of problem does CVE-2026-34972 cause in OpenFGA?
CVE-2026-34972 causes incorrect authorization decisions due to list-value cache-key collision during BatchCheck requests.
Is there a workaround for CVE-2026-34972 before upgrading?
There are no official workarounds for CVE-2026-34972; upgrading to a secure version is the recommended approach.