CVE-2026-55689

OpenFGA: OIDC audience validation skipped when --authn-oidc-audience is unset

CVSS 3.1 6.8 MEDIUMEUVD CVSS 3.1 6.8 CVSS 3.1 · [email protected] · Secondary 6.8 MEDIUMCVSS 3.1 · [email protected] · Primary 8.1 HIGHCVSS_V3 Publisher rating MODERATEFixed by github.com/openfga/openfga 1.18.0osv · severity unknownFixed by github.com/openfga/openfga 1.18.0KEV status unknown

Original advisory

cve-program · CVE-2026-55689

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-42710

Published

Read the publisher's advisory

nvd · CVE-2026-55689

Published

Read the publisher's advisory

osv · GHSA-hcxc-wf8j-23hv

Published

## Description OpenFGA's OIDC authenticator skipped JWT audience (`aud`) validation when no audience was configured. In deployments where one identity provider issues tokens for multiple services, a token minted for an unrelated service could authenticate to OpenFGA. ## Preconditions This applies if the following preconditions are met: 1. You run OpenFGA with `authn.method` set to `oidc`. 2. You configured `authn.oidc.issuer` but did **not** set `authn.oidc.audience` (`--authn-oidc-audience` / `OPENFGA_AUTHN_OIDC_AUDIENCE`). ## Fix Upgrade to OpenFGA 1.18.0 or greater. OpenFGA now refuses to start in `oidc` mode unless both `authn.oidc.issuer` and `authn.oidc.audience` are set, and the `aud` claim is always validated. ## Acknowledgements OpenFGA would like to thank https://github.com/0xVijay for the report.

Read the publisher's advisory

osv · GO-2026-5423

Published

OpenFGA: OIDC audience validation skipped when --authn-oidc-audience is unset in github.com/openfga/openfga

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

Advisory history

13 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

14 Nov 2026 07:08:10 UTC