Categories
CVE-2026-61709 medium CVSS 5.3

Vulnerability in github.com/openfga/openfga (CVE-2026-61709)

Summary

Vulnerability in github.com/openfga/openfga (CVE-2026-61709). Confidential information can be exposed externally. Mitigation: upgrade to 1.18.1 or later.

Original description

The description as published by the source.

Description

In OpenFGA, the ListUsers API could incorrectly return a user who should have been excluded.

Preconditions

This applies if all of the following are present:

  • The authorization model contains a relation defined as an intersection (and) where at least one operand is an exclusion of the form base but not excluded: e.g. rel1: (public_user but not blocked) and rel2
  • The base side of that exclusion is granted through a type-bound public wildcard (e.g. user:*).
  • A user excluded by the but not clause is also granted, via a concrete tuple, through another operand of the intersection.
  • Your application uses ListUsers to enumerate or enforce access

Fix

Upgrade to OpenFGA v1.18.1 or greater.

Acknowledgements

OpenFGA would like to thank @5ud0er for the detailed report.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61709 has been found in github.com/openfga/openfga.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: upgrade github.com/openfga/openfga to 1.18.1 or later.
If unsure, ask your IT team or search "github.com/openfga/openfga CVE-2026-61709" on the vendor's site.

CVE-2026-61709 (github.com/openfga/openfga) — CWE-281 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.18.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-281) exists in github.com/openfga/openfga.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/openfga/openfga.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.18.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/openfga/openfga' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/openfga/openfga' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/openfga/openfga を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/openfga/openfga to 1.18.1

    ステージング環境で 1.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/openfga/openfga
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details