Copyright © 2012 Red Hat, Inc. All rights reserved. Moderate 2026-07-09T21:06:22 openfga: OpenFGA: OIDC audience validation skipped when --authn-oidc-audience is unset 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N CWE-287

OpenFGA is an authorization/permission engine built for developers. Prior to 1.18.0, OpenFGA's OIDC authenticator skipped JWT audience validation when authn.method was set to oidc, authn.oidc.issuer was configured, and authn.oidc.audience was not set, allowing a token minted for an unrelated service by the same identity provider to authenticate to OpenFGA. This issue is fixed in 1.18.0.

OpenFGA is an authorization/permission engine built for developers. Prior to 1.18.0, when OpenFGA is configured to use OIDC authentication (authn.method=oidc, authn.oidc.issuer set) but authn.oidc.audience is left unset, the JWT audience claim on incoming bearer tokens is not validated. As a result, a validly-signed OIDC access token issued by the same identity provider for a completely different, unrelated application can be accepted by OpenFGA as a valid credential, allowing an attacker holding such a token to authenticate to OpenFGA and perform unauthorized authorization queries or writes. This issue is fixed in OpenFGA 1.18.0.

OpenFGA, when run with OIDC authentication enabled (--authn-oidc-issuer) but with --authn-oidc-audience left unset, does not validate the JWT audience claim on incoming bearer tokens. This means a validly-signed OIDC access token issued by the same identity provider for a completely different application/audience will be accepted by OpenFGA as a valid credential. An attacker who can obtain such a token, for example one issued to a lower-privileged or unrelated application at the same IdP, could use it to authenticate to OpenFGA and perform authorization queries or writes they should not be permitted to make. This flaw only affects deployments that explicitly enable OpenFGA's OIDC authentication method and leave --authn-oidc-audience unset. Deployments using OpenFGA's default (pre-shared key) authentication, or that embed OpenFGA purely as an internal library without exposing its standalone OIDC-authenticated API such as Grafana's Zanzana engine, are less likely to be exposed to this specific issue, though this has not been independently confirmed for every embedding product. Administrators running OpenFGA with OIDC authentication enabled should set --authn-oidc-audience to the expected audience value for their deployment, restricting accepted tokens to those issued for OpenFGA itself. Upgrading to OpenFGA 1.18.0 or later, which restores audience validation by default, is the preferred long-term remediation. Multicluster Global Hub Fix deferred multicluster-globalhub/multicluster-globalhub-grafana-rhel9 Red Hat Advanced Cluster Management for Kubernetes 2 Fix deferred rhacm2/acm-grafana-rhel9 Red Hat Ceph Storage 6 Fix deferred rhceph/rhceph-6-dashboard-rhel9 Red Hat Ceph Storage 7 Fix deferred rhceph/grafana-rhel9 Red Hat Ceph Storage 8 Fix deferred rhceph/grafana-rhel9 Red Hat Ceph Storage 9 Fix deferred rhceph/grafana-rhel10 Red Hat Enterprise Linux 10 Fix deferred grafana https://www.cve.org/CVERecord?id=CVE-2026-55689 https://nvd.nist.gov/vuln/detail/CVE-2026-55689 https://github.com/openfga/helm-ch https://github.com/openfga/helm-charts/releases/tag/openfga-0.3.9 https://github.com/openfga/openfga/commit/44596773b2e62738720ef215bf7fa04352954271 https://github.com/openfga/openfga/releases/tag/v1.18.0 https://github.com/openfga/openfga/security/advisories/GHSA-hcxc-wf8j-23hv