{"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-64529 in the wild and no public exploit code.","fix":"Upgrade github.com/authzed/spicedb to 1.45.2 or later.","what":"CVE-2025-64529 is a low-severity vulnerability in authzed spicedb, published on 10 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-64529 and fix it if it is affected.\n\nWhat it is: CVE-2025-64529 is a low-severity vulnerability in authzed spicedb, published on 10 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-64529 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.45.2\n- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.45.2\n- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.45.2\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-64529/ (Markdown: https://insights.sbomify.com/CVE-2025-64529/index.md)","id":"CVE-2025-64529","markdown":"https://insights.sbomify.com/CVE-2025-64529/index.md","name":"CVE-2025-64529","record":{"aliases":["GHSA-pm3x-jrhh-qcr7","GO-2025-4120"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SpiceDB authorization database","requires_auth":"none","summary":"Attackers can bypass authorization checks in SpiceDB by triggering silent failures in relationship writes under specific high-volume configurations.","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.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"SpiceDB is an open source database system for creating and managing security-critical application permissions. In versions prior to 1.45.2, users who use the exclusion operator somewhere in their authorization schema; have configured their SpiceDB server such that `--write-relationships-max-updates-per-call` is bigger than 6500; and issue calls to WriteRelationships with a large enough number of updates that cause the payload to be bigger than what their datastore allows; will receive a successful response from their `WriteRelationships` call, when in reality that call failed, and receive incorrect permission check results, if those relationships had to be read to resolve the relation involving the exclusion. Version 1.45.2 contains a patch for the issue. As a workaround, set `--write-relationships-max-updates-per-call` to `1000`.","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 WriteRelationships fails silently if payload is too big","id":"CVE-2025-64529","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"@apollo/composition has Improper Enforcement of Access Control on Interface Types and Fields","id":"CVE-2025-64530"},"packages":[{"ecosystem":"Go","fixed":["1.45.2"],"introduced":["0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":null,"source":"GHSA-pm3x-jrhh-qcr7"},{"ecosystem":"Go","fixed":["1.45.2"],"introduced":["0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GHSA-pm3x-jrhh-qcr7"},{"ecosystem":"Go","fixed":["1.45.2"],"introduced":["0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GO-2025-4120"}],"prev":{"headline":"Users are able to find users by name even when `enable_names` is off","id":"CVE-2025-64528"},"products":["spicedb"],"published":"2025-11-10","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-12","vendors":["authzed"]},"summary":"Attackers can bypass authorization checks in SpiceDB by triggering silent failures in relationship writes under specific high-volume configurations.","url":"https://insights.sbomify.com/CVE-2025-64529/"}