dbcve.org
Helm ChartsApplication · Openfga

CVE-2025-64751

HIGH · 8.8 CVSS v3.1 Published 2025-11-21
Fix available
A fix is available. Upgrade to 0.2.49 / 1.11.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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 a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. OpenFGA v1.4.0 to v1.11.0 ( openfga-0.1.34 <= Helm chart <= openfga-0.2.48, v.1.4.0 <= docker <= v.1.11.0) are vulnerable to improper policy enforcement when certain Check and ListObject calls are executed. This issue has been patched in version 1.11.1.

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 · moderate confidence

OpenFGA versions 1.4.0 through 1.11.0 contain an improper policy enforcement vulnerability in the Check and ListObject authorization API calls. This allows unauthorized access to resources that should be protected by the authorization engine, effectively bypassing configured permission policies.

MitigationUpgrade OpenFGA to version 1.11.1 or later. For Helm chart deployments, upgrade openfga-0.2.49 or later; for Docker, upgrade to v1.11.1 or later.

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.1.34, < 0.2.49
OpenfgaApplication
Affected:>= 1.4.0, < 1.11.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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 binary or container version
    Run `openfga version` for binary, or inspect container image tag with `docker images` or container runtime inspect
    Affected if Version is 1.4.0 through 1.11.0 (or image tag like v1.4.0 to v1.11.0)
  2. Check Helm chart version for Kubernetes deployments
    Run `helm list -n <namespace>` and `helm get values <release>`, or query Kubernetes: `kubectl get deployment -o yaml` or `kubectl get statefulset -o yaml`
    Affected if Helm chart version is 0.1.34 through 0.2.48
  3. Verify authorization model is configured
    Query the OpenFGA API: `GET /v1/authorization-models` or check if store contains authorization model definitions and tuples via `openfga tuple list`
    Affected if An authorization model ID exists and tuples (relations) are defined, indicating authorization policies are in effect
  4. Identify usage of vulnerable API endpoints
    Review application logs, API gateway metrics, or OpenFGA audit logs for calls to `/v1/stores/{store_id}/check` and `/v1/stores/{store_id}/list-objects` endpoints
    Affected if The Check or ListObject authorization APIs are being called to evaluate permissions

Environment is affected if OpenFGA version is 1.4.0-1.11.0 (or Helm chart 0.1.34-0.2.48) AND authorization policies are configured AND the Check or ListObject APIs are in use, allowing potential bypass of configured permissions.

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.2.49 / 1.11.1 or later
Fixed in 0.2.491.11.1
Interim mitigation

Upgrade OpenFGA to version 1.11.1 or later. For Helm chart deployments, upgrade openfga-0.2.49 or later; for Docker, upgrade to v1.11.1 or later.

Recommended fix High confidence

OpenFGA v1.11.1 and Helm chart 0.2.49

  1. Upgrade OpenFGA from any version >= 1.4.0 and < 1.11.1 to version 1.11.1 or later
  2. If using Helm charts, upgrade from any chart version >= 0.1.34 and < 0.2.49 to chart version 0.2.49 or later
  3. After upgrade, verify that Check and ListObject calls are enforcing policies correctly per the expected authorization model

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

Fix this in Helm Charts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64751 — 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-2025-64751 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