{"answers":{"affected":"3 open source packages ship an affected version, including github.com/authzed/spicedb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65111 in the wild and no public exploit code.","fix":"Upgrade github.com/authzed/spicedb to 1.47.1 or later.","what":"CVE-2025-65111 is a low-severity vulnerability in authzed spicedb, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65111 and fix it if it is affected.\n\nWhat it is: CVE-2025-65111 is a low-severity vulnerability in authzed spicedb, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-65111 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.47.1\n- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.47.1\n- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.47.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-2025-65111/ (Markdown: https://insights.sbomify.com/CVE-2025-65111/index.md)","id":"CVE-2025-65111","markdown":"https://insights.sbomify.com/CVE-2025-65111/index.md","name":"CVE-2025-65111","record":{"aliases":["GHSA-9m7r-g8hg-x3vr","GO-2025-4151"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SpiceDB permissions database","requires_auth":"none","summary":"SpiceDB may return incomplete permission results for specific union schemas, potentially allowing unauthorized access to resources.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spicedb","vendor":"authzed"}],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-277","name":"Insecure Inherited Permissions"}],"description":"SpiceDB is an open source database system for creating and managing security-critical application permissions. Prior to version 1.47.1, if a schema includes the following characteristics: permission defined in terms of a union (+) and that union references the same relation on both sides (but one side arrows to a different permission). Then SpiceDB may have missing LookupResources results when checking the permission. This only affects LookupResources; other APIs calculate permissionship correctly. The issue is fixed in version 1.47.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":"SpiceDB's LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results","id":"CVE-2025-65111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"PubNet Critical Authentication Bypass Allows Unauthenticated Package Upload and Identity Spoofing","id":"CVE-2025-65112"},"packages":[{"ecosystem":"Go","fixed":["1.47.1"],"introduced":["0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":null,"source":"GHSA-9m7r-g8hg-x3vr"},{"ecosystem":"Go","fixed":["1.47.1"],"introduced":["0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GHSA-9m7r-g8hg-x3vr"},{"ecosystem":"Go","fixed":["1.47.1"],"introduced":["0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GO-2025-4151"}],"prev":{"headline":"Vega XSS via expression abusing vlSelectionTuples function array map calls in environments with satisfactory function gadgets in the global scope","id":"CVE-2025-65110"},"products":["spicedb"],"published":"2025-11-21","related":[{"cvss_score":8.7,"headline":"SpiceDB binding metrics port to untrusted networks and can leak command-line flags","id":"CVE-2023-29193","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":8.1,"headline":"Lookup operations do not take into account wildcards in SpiceDB","id":"CVE-2022-21646","kev_date_added":null,"published":"2022-01-11"},{"cvss_score":7.3,"headline":"Integer overflow in chunking helper causes dispatching to miss elements or panic","id":"CVE-2024-27101","kev_date_added":null,"published":"2024-03-01"},{"cvss_score":6,"headline":"SpiceDB: SPICEDB_DATASTORE_CONN_URI is leaked on startup logs","id":"CVE-2026-40091","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":4.2,"headline":"`SPICEDB_DATASTORE_CONN_URI` is leaked when URI cannot be parsed","id":"CVE-2023-46255","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":3.7,"headline":"SpiceDB checks involving relations with caveats can result in no permission when permission is expected","id":"CVE-2025-49011","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":3.7,"headline":"Multiple caveats on resources of the same type can result in no permission when permission is expected","id":"CVE-2024-46989","kev_date_added":null,"published":"2024-09-18"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-24","vendors":["authzed"]},"summary":"SpiceDB may return incomplete permission results for specific union schemas, potentially allowing unauthorized access to resources.","url":"https://insights.sbomify.com/CVE-2025-65111/"}