cve.bz

CVE-2026-61709 openfga openfga: Improper Preservation of Permissions

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in openfga openfga. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/openfga/openfga 1.18.1.

On this page
OpenFGA is an authorization and permission engine built for developers. Prior to 1.18.1, the ListUsers API could return a user that should have been excluded when an authorization relation used an intersection containing a base but not excluded operand, the base was granted through a type-bound public wildcard, and the excluded user also had a concrete tuple through another intersection operand. In pkg/server/commands/listusers/list_users_rpc.go, expandIntersection counted the concrete tuple and wildcard without first rejecting entries in excludedUsersMap. Applications that used ListUsers to enumerate or enforce access could therefore treat an excluded user as authorized. This issue is fixed in version 1.18.1.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-281 Improper Preservation of Permissions
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-61709 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61709?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61709?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61709 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
openfga< 1.18.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g3pg-frfm-pr2mGogithub.com/openfga/openfga<1.18.11.18.1
GO-2026-6488Gogithub.com/openfga/openfga<1.18.11.18.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hathummingbird:1grafana12.40:12.4.10-0.5.hum1RHSA-2026:68777
Red Hathummingbird:1grafana12.40:12.4.10-0.6.hum1RHSA-2026:68821
Red Hathummingbird:1grafana13.10:13.1.6-0.3.hum1RHSA-2026:71040
Red Hathummingbird:1grafana13.20:13.2.1-0.4.hum1RHSA-2026:67605
openSUSETumbleweedgrafana12.4.15-1.1openSUSE-SU-2026:12582-1

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is in OpenFGA's ListUsers API, which could return a user who should have been excluded by a but-not clause when an intersection used a type-bound public wildcard. Red Hat does not ship OpenFGA as a standalone product. The code is bundled in Grafana's experimental Zanzana authorization engine and Grafana is embedded in Red Hat Ceph Storage dashboards, Red Hat Advanced Cluster Management, Multicluster Global Hub, and the RHEL grafana package. Zanzana is disabled by default in upstream Grafana. Grafana's own authorization path uses Check and ListObjects, not ListUsers, so the vulnerable API is not the enforcement path in these products.

Red Hat's mitigation

No product-side mitigation is required while Zanzana remains disabled, which is the default. If Zanzana has been turned on, do not use ListUsers results as an access-control decision; use Check for each user and object until Grafana vendors OpenFGA 1.18.1 or later.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana13-2-main-13.2.1-0.4.hum1Fixed 2026-09-15RHSA-2026:67605
Red Hat Hardened Imagesgrafana12-4-main-12.4.10-0.5.hum1Fixed 2026-09-17RHSA-2026:68777
Red Hat Hardened Imagesgrafana12-4-main-12.4.10-0.6.hum1Fixed 2026-09-18RHSA-2026:68821
Red Hat Hardened Imagesgrafana13-1-main-13.1.6-0.3.hum1Fixed 2026-09-23RHSA-2026:71040
Red Hat Hardened Imagesgrafana13-1-main-13.1.6-0.4.hum1Fixed 2026-09-28RHSA-2026:72498
Multicluster Global Hubmulticluster-globalhub/multicluster-globalhub-grafana-rhel9Fix deferred
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/acm-grafana-rhel9Fix deferred
Red Hat Ceph Storage 6rhceph/rhceph-6-dashboard-rhel9Out of support scope
Red Hat Ceph Storage 7rhceph/grafana-rhel9Fix deferred
Red Hat Ceph Storage 8rhceph/grafana-rhel9Fix deferred
Red Hat Ceph Storage 9rhceph/grafana-rhel10Out of support scope
Red Hat Enterprise Linux 10grafanaFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-61709.

References

Check your stackJSON