dbcve.org
Helm ChartsApplication · Openfga

CVE-2025-55213

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-18
Fix available
A fix is available. Upgrade to 0.2.42 / 1.9.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.9.3 to v1.9.4 ( openfga-0.2.40 <= Helm chart <= openfga-0.2.41, v1.9.3 <= docker <= v.1.9.4) are vulnerable to improper policy enforcement when certain Check and ListObject calls are executed. This vulnerability is fixed in 1.9.5.

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.9.3 through 1.9.4 contain an improper policy enforcement vulnerability affecting the Check and ListObject authorization APIs. This allows unauthorized access to resources when certain authorization queries are executed, bypassing the configured permission model.

MitigationUpgrade to OpenFGA v1.9.5 or later. For Helm chart deployments, upgrade beyond openfga-0.2.41; for Docker deployments, upgrade beyond the v1.9.4 tag.

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.2.40, < 0.2.42
OpenfgaApplication
Affected:>= 1.9.3, < 1.9.5

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine OpenFGA server version
    Run 'openfga version' for CLI or check the Docker image tag (e.g., 'docker images | grep openfga') or Helm chart version (e.g., 'helm list' and 'helm get values <release>')
    Affected if Version is 1.9.3 or 1.9.4 for the server, or chart version 0.2.40 or 0.2.41 for Helm deployments
  2. Confirm OpenFGA service is running
    Check running process (e.g., 'ps aux | grep openfga') or Kubernetes pod (e.g., 'kubectl get pods -l app.kubernetes.io/name=openfga')
    Affected if OpenFGA service is running with a vulnerable version from step 1
  3. Identify if Check API is in use
    Review application logs for POST requests to /stores/{store_id}/check endpoint, or inspect API gateway/middleware logs for authorization checks
    Affected if The Check authorization API endpoint is being called against the affected OpenFGA instance
  4. Identify if ListObjects API is in use
    Review application logs for POST requests to /stores/{store_id}/list-objects endpoint, or inspect API traffic for list-objects calls
    Affected if The ListObjects authorization API endpoint is being called against the affected OpenFGA instance

You are affected if you are running OpenFGA version 1.9.3 or 1.9.4 (or Helm chart 0.2.40 or 0.2.41) AND your applications use the Check or ListObjects authorization APIs.

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.42 / 1.9.5 or later
Fixed in 0.2.421.9.5
Vendor patch github.com →
Interim mitigation

Upgrade to OpenFGA v1.9.5 or later. For Helm chart deployments, upgrade beyond openfga-0.2.41; for Docker deployments, upgrade beyond the v1.9.4 tag.

Recommended fix High confidence

OpenFGA v1.9.5 or Helm chart 0.2.42

  1. For Docker deployments: Pull and run the fixed OpenFGA v1.9.5 container image
  2. For Helm deployments: Upgrade the Helm chart to version 0.2.42 which bundles OpenFGA v1.9.5 using 'helm upgrade <release-name> openfga/openfga --version 0.2.42'
  3. After upgrade, verify the OpenFGA service is running: check container logs and confirm the version displayed matches v1.9.5
  4. Test authorization workflows (Check and ListObject calls) to confirm the vulnerability is remediated
Caveat No breaking changes documented in the release notes for v1.9.5

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 / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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