How severe is GHSA-m3q4-7qmj-657m?

No CVSS score has been assigned to GHSA-m3q4-7qmj-657m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m3q4-7qmj-657m?

GHSA-m3q4-7qmj-657m affects the following packages: github.com/openfga/openfga (Go). Ecosystems affected: Go.

How do I fix GHSA-m3q4-7qmj-657m?

Update github.com/openfga/openfga to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3q4-7qmj-657m is resolved across your whole dependency graph.

How do I detect GHSA-m3q4-7qmj-657m 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-m3q4-7qmj-657m 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-m3q4-7qmj-657m actively exploited in the wild?

No public exploit code has been indexed for GHSA-m3q4-7qmj-657m 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-m3q4-7qmj-657m?

GHSA-m3q4-7qmj-657m has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th 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-m3q4-7qmj-657m?

GHSA-m3q4-7qmj-657m 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-m3q4-7qmj-657m published, and has it been updated?

GHSA-m3q4-7qmj-657m was published on December 20, 2022 and was last updated on August 21, 2024. 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-m3q4-7qmj-657m

Fix: openfga/openfga#422

GHSA-m3q4-7qmj-657m 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-2022-23542GO-2022-1179

Published

Dec 20, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-m3q4-7qmj-657m.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% 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

During our internal security assessment, it was discovered that OpenFGA versions v0.3.0 is vulnerable to authorization bypass under certain conditions.

Am I Affected?

You are affected by this vulnerability if all of the following applies:

You are using OpenFGA v0.3.0
You created a model using modeling language v1.1 that applies a type restriction to an object e.g. define viewer: [user]
You created tuples based on the aforementioned model, e.g. document:1#viewer@user:jon
You updated the previous model by adding a new type and replacing the previous restriction with the newly added type e.g. define viewer: [employee]
You use the tuples created against the first model (step 3) and issue checks against the updated model e.g. user=user:jon, relation=viewer, object:document:1

How to fix that?

Upgrade to version v0.3.1

Backward Compatibility

This update is backward compatible.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openfga/openfga`	≥ 0.3.0&&< 0.3.1	0.3.1`go get github.com/openfga/openfga@v0.3.1`

Affected Products

1 product · 1 configurations

Application

openfgaopenfga

< 0.3.1

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 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3q4-7qmj-657m 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 During our internal security assessment, it was discovered that OpenFGA versions v0.3.0 is vulnerable to authorization bypass under certain conditions. ### Am I Affected? You are affected by this vulnerability if **all** of the following applies: 1. You are using OpenFGA v0.3.0 2. You created a model using modeling language v1.1 that applies a type restriction to an object e.g. `define viewer: [user]` 3. You created tuples based on the aforementioned model, e.g. `document:1#viewer@user:jon` 4. You updated the previous model by adding a new type and replacing the previous restri

O3 Security · Impact-Aware SCA

Is GHSA-m3q4-7qmj-657m in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works