# CVE-2026-41131: OpenFGA has Improper Policy Enforcement

Source: https://junglewise.ai/threats/cve-2026-41131-openfga-has-improper-policy-enforcement  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-22. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-41131 · Severity: medium · CVSS 5 · Published 2026-04-22

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.

Technologies: [github.com/openfga/openfga (Go)](https://junglewise.ai/threats/technologies/github-com-openfga-openfga), [OpenFGA](https://junglewise.ai/threats/technologies/openfga), [Openfga (Helm-Charts)](https://junglewise.ai/threats/technologies/openfga-helm-charts). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [OpenFGA](https://junglewise.ai/threats/vendors/openfga).

## Quick answers

**Is CVE-2026-41131 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-41131 being exploited in the wild.

**How severe is CVE-2026-41131?** Medium severity, with a CVSS score of 5, published 22 April 2026.

**Which products and versions are affected?** github.com/openfga/openfga (Go) < 1.14.1, SEMVER:introduced=0,fixed=1.14.1.

**Is there a fix for CVE-2026-41131?** Yes. github.com/openfga/openfga (Go): upgrade to 1.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-41131?** Check whether you run github.com/openfga/openfga (Go), OpenFGA or Openfga (Helm-Charts) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/openfga/openfga (Go): upgrade to 1.14.1 or later

  ```sh
  go get github.com/openfga/openfga@v1.14.1
  ```


## Affected products

- github.com/openfga/openfga (Go) < 1.14.1, SEMVER:introduced=0,fixed=1.14.1
- OpenFGA
- Openfga (Helm-Charts)

## Identifiers

- CVE-2026-41131
- GHSA-57j5-qwp2-vqp6
- GO-2026-5136

## References

- [https://api.github.com/users/bugbunny-research](https://api.github.com/users/bugbunny-research)
- [https://github.com/bugbunny-research](https://github.com/bugbunny-research)
- [https://api.github.com/users/bugbunny-research/gists%7B/gist_id%7D](https://api.github.com/users/bugbunny-research/gists%7B/gist_id%7D)
- [https://api.github.com/users/bugbunny-research/repos](https://api.github.com/users/bugbunny-research/repos)
- [https://avatars.githubusercontent.com/u/262839898?v=4](https://avatars.githubusercontent.com/u/262839898?v=4)
- [https://api.github.com/users/bugbunny-research/events%7B/privacy%7D](https://api.github.com/users/bugbunny-research/events%7B/privacy%7D)

## Related threats

- [OpenFGA ListUsers incorrect authorization in intersection exclusions](https://junglewise.ai/threats/cve-2026-61709-openfga-listusers-incorrect-authorization-in-intersection)
- [OpenFGA improper authentication via JWT audience skip in OIDC authenticator](https://junglewise.ai/threats/cve-2026-55689-openfga-improper-authentication-via-jwt-audience-skip-in-oidc)
- [OpenFGA case sensitivity mismatch in MySQL datastore](https://junglewise.ai/threats/cve-2026-55170-openfga-case-sensitivity-mismatch-in-mysql-datastore)
- [OpenFGA cache key collision in iterator caching](https://junglewise.ai/threats/cve-2026-48096-openfga-cache-key-collision-in-iterator-caching)
- [OpenFGA API key exposure in playground endpoint](https://junglewise.ai/threats/cve-2026-40293-openfga-api-key-exposure-in-playground-endpoint)