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.
CVE-2026-55689
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- —
- EPSS
- 22.3%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
July 14, 2026
Advisory Details (4)
Auto-updated Jul 9, 2026v1.18.0
Patch available: openfga/openfga v1.18.0
https://github.com/openfga/openfga/releases/tag/v1.18.0openfga-0.3.9
Patch available: openfga/helm-charts openfga-0.3.9
https://github.com/openfga/helm-charts/releases/tag/openfga-0.3.9commit 44596773b2e6 (openfga/openfga)
Fix landed in openfga/openfga commit 44596773b2e6 — awaiting tagged release
https://github.com/openfga/openfga/commit/44596773b2e62738720ef215bf7fa04352954271OpenFGA Improper Authentication · Advisory · openfga/openfga · GitHub
https://github.com/openfga/openfga/security/advisories/GHSA-hcxc-wf8j-23hvVendor Advisories for CVE-2026-55689(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/openfga/openfga | — | 1.18.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 16:08 UTCEG score recompute▲ 1.30
- 2026-07-14 01:43 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-06-19 14:57 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55689?
When was CVE-2026-55689 disclosed?
Is CVE-2026-55689 actively exploited?
What is the CVSS score of CVE-2026-55689?
How do I remediate CVE-2026-55689?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55689
Is Your Infrastructure Affected by CVE-2026-55689?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.