CVE-2022-23542 json
OpenFGA Authorization Bypass
published 2022-12-20 3 y ago modified 2026-06-17 4 mo ago also GHSA-m3q4-7qmj-657m , GO-2022-1179 , EUVD-2022-7675
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
OpenFGA is an authorization/permission engine built for developers and inspired by Google Zanzibar. During an internal security assessment, it was discovered that OpenFGA version 0.3.0 is vulnerable to authorization bypass under certain conditions. This issue has been patched in version 0.3.1 and is backward compatible.
Patch / fix
- go github.com/openfga/openfga 0.3.1
- openfga openfga 0.3.1
- github.com/openfga/openfga#422 pull request
- github.com/openfga/openfga/releases/tag/v0.3.1 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/openfga/openfga | >=0.3.0, <0.3.1 |
0.3.1 |
Affected products
- openfga openfga
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
-
github.com
/openfga/openfga/pull/422
web, patch, third-party-advisory
-
github.com
/openfga/openfga/security/advisories/GHSA-m3q4-7qmj-657m
web, third-party-advisory, advisory
-
github.com
/openfga/openfga/releases/tag/v0.3.1
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-23542
advisory
-
github.com
/openfga/openfga
package
Sources
- CVE List CVE-2022-23542
- GitHub Advisory GHSA-m3q4-7qmj-657m
- NVD CVE-2022-23542
- OSV GO-2022-1179
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.