dbcve.org
Helm ChartsApplication · Openfga

CVE-2026-41131

MEDIUM · 5.0 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 0.3.1 / 1.14.1 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In OpenFGA versions prior to 1.14.1, when authorization models use conditions combined with caching enabled, different check requests can generate identical cache keys. This causes the system to incorrectly reuse cached authorization results from one request for a subsequent, different request, potentially allowing unauthorized access.

MitigationUpgrade OpenFGA to version 1.14.1 or later. If immediate upgrade is not possible, consider disabling caching for models that use conditions until the upgrade can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Helm ChartsApplication
Affected:< 0.3.1
OpenfgaApplication
Affected:< 1.14.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenFGA server version
    Run `openfga version` if CLI is available, or check the image tag/deployment manifest for the installed OpenFGA version. Also check via API: send a GET request to `/healthz` or check response headers for version info.
    Affected if Version is earlier than 1.14.1 (e.g., 1.14.0, 1.13.x, 1.12.x, etc.)
  2. Check OpenFGA Helm Chart version
    Run `helm list -n <namespace>` and inspect the CHART version column, or check your Helm values.yaml and deployment manifests for the chart version.
    Affected if Helm Chart version is earlier than 0.3.1
  3. Verify if request caching is enabled
    Inspect your OpenFGA configuration (config.yaml, environment variables, or Helm values). Look for `cache` settings - typically `cache.enabled: true` or `OPENFGA_CACHE_ENABLED=true`. Check your deployment configuration files.
    Affected if Caching is enabled (cache.enabled is true or cache-related settings are present and active)
  4. Identify if authorization models use conditions
    List all authorization models via API: `GET /v1/authorization-models?store_id=<store_id>`. Inspect the returned models for the presence of the `conditions` field in any type definitions. Alternatively, check your model definition files (.fga.yaml) for condition definitions.
    Affected if Any deployed authorization model contains a `conditions` block defining one or more named conditions (e.g., condition ip_range, condition time_window, etc.)

A user is affected if they run OpenFGA version < 1.14.1 (or Helm Chart < 0.3.1) AND have both caching enabled AND use authorization models that define conditions - the vulnerability requires all three conditions to be present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.3.1 / 1.14.1 or later
Fixed in 0.3.11.14.1
Interim mitigation

Upgrade OpenFGA to version 1.14.1 or later. If immediate upgrade is not possible, consider disabling caching for models that use conditions until the upgrade can be completed.

Recommended fix High confidence

OpenFGA v1.14.1 (or Helm Charts v0.3.1)

  1. 1. Identify which OpenFGA deployment method is in use: direct binary/container (OpenFGA) or Helm chart deployment (Helm Charts)
  2. 2. For direct OpenFGA deployment: check current version using `openfga version` or inspect the container image tag
  3. 3. For Helm Charts deployment: check current chart version using `helm list` and `helm show chart <release-name>`
  4. 4. If running OpenFGA < 1.14.1, upgrade to version 1.14.1 or later
  5. 5. If using Helm Charts < 0.3.1, upgrade the chart to version 0.3.1 or later which bundles the fixed OpenFGA version
  6. 6. After upgrade, verify the new version is running correctly
  7. 7. If using model conditions with caching, validate that different requests now produce distinct cache keys and cached results are not incorrectly reused
Caveat Minor version upgrade - review release notes for any breaking changes in v1.14.x

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Helm Charts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41131 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data