OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.0 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2026-34972: 0.22% estimated exploitation activity in the next 30 days; percentile 12.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

7 Apr 2026, 18:05 UTC

Last modified by the source

7 Apr 2026, 18:05 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jwvj-g8pc-cx45

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34972

Advisory: OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision
IDs: CVE-2026-34972, GHSA-jwvj-g8pc-cx45
Record: https://patchnext.com/advisories/cve-2026-34972 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openfga/openfga 1.14.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openfga/openfga: affected >= 1.8.0, <= 1.13.1; fixed in 1.14.0

## Suggested inspection (read-only)
- Go github.com/openfga/openfga: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openfga/openfga.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jwvj-g8pc-cx45 (GitHub-reviewed advisory GHSA-jwvj-g8pc-cx45 lists affected ranges: Go github.com/openfga/openfga >=1.8.0 <=1.13.1)

Commands are suggestions: review each one before running it.