{"answers":{"affected":"3 open source packages ship an affected version, including github.com/openfga/openfga.","exploited":"There is no known exploitation of CVE-2026-61709 in the wild and no public exploit code.","fix":"Upgrade github.com/openfga/openfga to 1.18.1 or later.","what":"CVE-2026-61709 is a medium-severity missing authorization vulnerability in openfga, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61709 and fix it if it is affected.\n\nWhat it is: CVE-2026-61709 is a medium-severity missing authorization vulnerability in openfga, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61709 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/openfga/openfga (Go): affected all versions; fixed in 1.18.1\n- github.com/openfga/openfga (Go): affected all versions; fixed in 1.18.1\n- github.com/openfga/openfga (Go): affected all versions; fixed in 1.18.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61709/ (Markdown: https://insights.sbomify.com/CVE-2026-61709/index.md)","id":"CVE-2026-61709","markdown":"https://insights.sbomify.com/CVE-2026-61709/index.md","name":"CVE-2026-61709","record":{"aliases":["CLEANSTART-2026-LI79671","ECHO-cd63-9789-8fd2","GHSA-g3pg-frfm-pr2m","GO-2026-6488","MINI-2m3c-29mw-r27x","MINI-2p49-w43h-pgh3","MINI-2rmx-whcm-jjfv","MINI-47r4-r96q-2jpg","MINI-59q3-wmfx-3f48","MINI-6h25-v7jm-vq32","MINI-6h4h-4jmh-3w9p","MINI-82x5-4gvm-f6gw","MINI-8v8w-5jqj-289q","MINI-9wv3-3xv8-mh9x","MINI-f66q-gq5g-rrhq","MINI-gqxf-c3w5-7xv2","MINI-gr44-xf83-mqqq","MINI-h4jq-pg3v-qcf9","MINI-h63j-m4jp-9x7x","MINI-phrh-437h-h49x","MINI-r3x9-vw98-r4fw","MINI-rr2w-9mh2-gf42","MINI-vfmv-9jjj-qjrg","MINI-w83j-qrmr-ggff","MINI-wm74-7c73-244q","MINI-xp7c-x249-f25f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenFGA authorization engine","requires_auth":"low_privilege","summary":"Attackers can bypass authorization checks in OpenFGA's ListUsers API when specific intersection and exclusion logic is used, gaining unauthorized access.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-281","name":"Improper Preservation of Permissions"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenFGA: ListUsers returns a deliberately-excluded user when a `but not` exclusion under a type-bound wildcard is intersected (`and`) with another relation that also grants that user","id":"CVE-2026-61709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"BuildKit: Custom frontend could bypass Seccomp/AppArmor","id":"CVE-2026-61711"},"packages":[{"ecosystem":"Go","fixed":["1.18.1"],"introduced":["0"],"last_affected":[],"package":"github.com/openfga/openfga","purl":null,"source":"GHSA-g3pg-frfm-pr2m"},{"ecosystem":"Go","fixed":["1.18.1"],"introduced":["0"],"last_affected":[],"package":"github.com/openfga/openfga","purl":"pkg:golang/github.com/openfga/openfga","source":"GHSA-g3pg-frfm-pr2m"},{"ecosystem":"Go","fixed":["1.18.1"],"introduced":["0"],"last_affected":[],"package":"github.com/openfga/openfga","purl":"pkg:golang/github.com/openfga/openfga","source":"GO-2026-6488"}],"prev":{"headline":"SOCFortress CoPilot: Stored case-report template injection permits backend code execution","id":"CVE-2026-61707"},"products":["openfga"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["openfga"]},"summary":"Attackers can bypass authorization checks in OpenFGA's ListUsers API when specific intersection and exclusion logic is used, gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-61709/"}