CVE-2025-65111: SpiceDB Remote Code Execution Vulnerability
LOWCVE-2025-65111 is a LOW remote code execution vulnerability (CWE-277: Insecure Inherited Permissions) affecting SpiceDB libraries in the Go ecosystem. The issue involves lookupresources with multiple entrypoints across different definitions can return incomplete results. Remediation is available by upgrading affected packages to version 1.47.1.
CVE-2025-65111 at a Glance
How to Fix CVE-2025-65111
To remediate this vulnerability, upgrade all affected SpiceDB dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/authzed/spicedb to 1.47.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/authzed/spicedb
How to Check if You Are Affected
To determine whether your application is affected by CVE-2025-65111, inspect your project dependencies for SpiceDB:
inspect dependencies for github.com/authzed/spicedb
Analyze the terminal output to locate any version of SpiceDB in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.47.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-277: Insecure Inherited Permissions, where a product defines a set of insecure permissions that are inherited by objects that are created by the program. In SpiceDB, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-65111 Affected SpiceDB Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/authzed/spicedb
|
Go |
< 1.47.1
|
1.47.1
|
References
Frequently Asked Questions
What is CVE-2025-65111?
Which SpiceDB versions are affected?
What version fixes CVE-2025-65111?
Is github.com/authzed/spicedb affected?
What CWE is associated with CVE-2025-65111?
How can I check Go dependencies for CVE-2025-65111?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9m7r-g8hg-x3vr",
"modified" : "2026-05-14T20:54:49Z",
"published" : "2025-11-21T18:06:00Z",
"aliases" : [ "CVE-2025-65111" ],
"summary" : "SpiceDB: LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results",
"details" : "### Impact\n\nIf your schema includes the following characteristics:\n\n1. You have a permission defined in terms of a union (`+`)\n1. That union references the same relation on both sides, but one side arrows to a different permission\n\nThen you might have missing `LookupResources` results when checking the permission. This only affects `LookupResources`; other APIs calculate permissionship correctly.\n\nA small concrete example:\n\n```\nrelation doer_of_things: user | group#member\npermission do_the_thing = doer_of_things + doer_of_things->admin\n```\n\nA CheckPermission on `do_the_thing` will return the correct permissionship, but a LookupResources on `do_the_thing` may miss resources.\n\n#### A Comprehensive Example\n\nIf you have a schema with a structure like this:\n\n```\ndefinition special_user {}\n\ndefinition user {\n relation special_user_mapping: special_user\n permission special_user = special_user_mapping\n}\ndefinition group {\n relation member: user\n permission membership = member + member->special_user\n}\n\ndefinition system {\n relation viewer: user | group#membership\n // This is the problematic permission\n permission view = viewer + viewer->special_user\n}\n```\n\nAnd these relationships:\n```\nsystem:somesystem#viewer@group:somegroup#membership\ngroup:somegroup#member@user:someuser1\nuser:someuser1#special_user_mapping@special_user:specialuser\n```\n\nAnd you call LookupResources with:\n```\nsubject_type: user\nsubject_id: someuser1\npermission: view\nresource_type: system\n```\n\nYou would expect to receive `system:somesystem` in the results, but you do not.\n\nNote that this only applies to `LookupResources`; if you `CheckPermission` for that resource specifically, it will return `HasPermission`.\n\n### Patches\n\nThe issue is fixed in v1.47.1. Upgrading to this version will remediate this issue.\n\n### Workarounds\nN/A\n\n### References\nN/A",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/authzed/spicedb"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.47.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/authzed/spicedb/security/advisories/GHSA-9m7r-g8hg-x3vr"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-65111"
}, {
"type" : "WEB",
"url" : "https://github.com/authzed/spicedb/commit/8c2edbe1e7bd3851fa2138f4cc344bfde986dcf2"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/authzed/spicedb"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-277" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-11-21T18:06:00Z",
"nvd_published_at" : "2025-11-21T22:16:33Z"
}
}