How severe is GHSA-g4v5-6f5p-m38j?

No CVSS score has been assigned to GHSA-g4v5-6f5p-m38j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g4v5-6f5p-m38j?

GHSA-g4v5-6f5p-m38j affects the following packages: github.com/openfga/openfga (Go). Ecosystems affected: Go.

How do I fix GHSA-g4v5-6f5p-m38j?

Update github.com/openfga/openfga to 1.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4v5-6f5p-m38j is resolved across your whole dependency graph.

How do I detect GHSA-g4v5-6f5p-m38j in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openfga/openfga, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g4v5-6f5p-m38j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g4v5-6f5p-m38j actively exploited in the wild?

No public exploit code has been indexed for GHSA-g4v5-6f5p-m38j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g4v5-6f5p-m38j?

GHSA-g4v5-6f5p-m38j has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g4v5-6f5p-m38j?

GHSA-g4v5-6f5p-m38j is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g4v5-6f5p-m38j published, and has it been updated?

GHSA-g4v5-6f5p-m38j was published on February 19, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

OpenFGA Authorization BypassGHSA-g4v5-6f5p-m38j

Fix: openfga/openfga@0aee4f4

GHSA-g4v5-6f5p-m38j is a CWE-285 vulnerability in github.com/openfga/openfga. A fix is available for github.com/openfga/openfga — see the affected versions and patch details below.

Also known asCVE-2025-25196GO-2025-3470

Published

Feb 19, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g4v5-6f5p-m38j.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/openfga/openfga

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Overview OpenFGA v1.8.4 or previous (Helm chart < openfga-0.2.22, docker < v.1.8.5) are vulnerable to authorization bypass when certain Check and ListObject calls are executed.

Am I Affected? If you are using OpenFGA v1.8.4 or previous, specifically under the following conditions, you are affected by this authorization bypass vulnerability:

Calling Check API or ListObjects with a model that has a relation directly assignable to both public access AND userset with the same type, and
A type bound public access tuple is assigned to an object, and
userset tuple is not assigned to the same object, and
Check request's user field is a userset that has the same type as the type bound public access tuple's user type

Fix Upgrade to v1.8.5. This upgrade is backwards compatible.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openfga/openfga`	all versions	1.8.5`go get github.com/openfga/openfga@v1.8.5`

Affected Products

2 products · 2 configurations

Application

helm chartsopenfga

< 0.2.22

range

Application

openfgaopenfga

< 1.8.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openfga/openfga, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openfga/openfga to 1.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4v5-6f5p-m38j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Overview OpenFGA v1.8.4 or previous (Helm chart < openfga-0.2.22, docker < v.1.8.5) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Am I Affected? If you are using OpenFGA v1.8.4 or previous, specifically under the following conditions, you are affected by this authorization bypass vulnerability: - Calling Check API or ListObjects with a model that has a relation [directly assignable](https://openfga.dev/docs/concepts#what-is-a-directly-related-user-type) to both [public access](https://openfga.dev/docs/concepts#what-is-type-bound-public-access) A

O3 Security · Impact-Aware SCA

Is GHSA-g4v5-6f5p-m38j in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works