github.com/openfga/openfga

CVE-2026-41131

CVE-2026-41131 is a medium-severity incorrect authorization vulnerability in github.com/openfga/openfga (go), affecting versions < 1.14.1. It is fixed in 1.14.1.

Key facts
CVSS score
5.0
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/openfga/openfga
Fixed in
1.14.1
Disclosed
2026

Summary

Description In OpenFGA, 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. Am I Affected? Users are affected if their applications meet the following preconditions: The model has relations which rely on condition evaluation. Caching is enabled. Fix Upgrade to OpenFGA v1.14.1. Acknowledgement OpenFGA would like to thank @bugbunny-research for the detailed report.

Impact

What is incorrect authorization?

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Severity and exposure

CVE-2026-41131 has a CVSS score of 5.0 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (1.14.1). Upgrading removes the vulnerable code path.

Affected versions

go

  • github.com/openfga/openfga (< 1.14.1)

Security releases

  • github.com/openfga/openfga → 1.14.1 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-41131 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-41131 is reachable in your applications. Get a demo

Remediation advice

Upgrade github.com/openfga/openfga to 1.14.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-41131

What is CVE-2026-41131?

CVE-2026-41131 is a medium-severity incorrect authorization vulnerability in github.com/openfga/openfga (go), affecting versions < 1.14.1. It is fixed in 1.14.1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2026-41131?

CVE-2026-41131 has a CVSS score of 5.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/openfga/openfga are affected by CVE-2026-41131?

github.com/openfga/openfga (go) versions < 1.14.1 is affected.

Is there a fix for CVE-2026-41131?

Yes. CVE-2026-41131 is fixed in 1.14.1. Upgrade to this version or later.

Is CVE-2026-41131 exploitable, and should I be worried?

Whether CVE-2026-41131 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-41131 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-41131?

Upgrade github.com/openfga/openfga to 1.14.1 or later.

Stop the waste.
Protect your environment with Kodem.