CVE-2025-65111: SpiceDB: LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results
Impact If your schema includes the following characteristics: 1. You have a permission defined in terms of a union (+) 1. That union references the same relation on both sides, but one side arrows to a different permission Then you might have missing LookupResources results when checking the permission. This only affects LookupResources; other APIs calculate permissionship correctly.
Published Nov 21, 2025 · Updated May 14, 2026
Affected packages
github.com/authzed/spicedb
- Ecosystem
- Go
- Affected
- < 1.47.1
- Fixed in
- 1.47.1
- Check
go list -m github.com/authzed/spicedb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
If your schema includes the following characteristics:
- You have a permission defined in terms of a union (
+) - That union references the same relation on both sides, but one side arrows to a different permission
Then you might have missing LookupResources results when checking the permission. This only affects LookupResources; other APIs calculate permissionship correctly.
A small concrete example:
relation doer_of_things: user | group#member
permission do_the_thing = doer_of_things + doer_of_things->adminA CheckPermission on do_the_thing will return the correct permissionship, but a LookupResources on do_the_thing may miss resources.
A Comprehensive Example
If you have a schema with a structure like this:
definition special_user {}
definition user {
relation special_user_mapping: special_user
permission special_user = special_user_mapping
}
definition group {
relation member: user
permission membership = member + member->special_user
}
definition system {
relation viewer: user | group#membership
// This is the problematic permission
permission view = viewer + viewer->special_user
}And these relationships:
system:somesystem#viewer@group:somegroup#membership
group:somegroup#member@user:someuser1
user:someuser1#special_user_mapping@special_user:specialuserAnd you call LookupResources with:
subject_type: user
subject_id: someuser1
permission: view
resource_type: systemYou would expect to receive system:somesystem in the results, but you do not.
Note that this only applies to LookupResources; if you CheckPermission for that resource specifically, it will return HasPermission.
Patches
The issue is fixed in v1.47.1. Upgrading to this version will remediate this issue.
Workarounds
N/A
References
N/A
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-55866
SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected
low3.7Jun 19, 2026CVE-2026-46668
SpiceDB: Caveat structures with nested lists can result in improper cache reuse
low2.3May 21, 2026CVE-2026-40091
SpiceDB's SPICEDB_DATASTORE_CONN_URI is leaked on startup logs
medium6.0Apr 14, 2026GHSA-vhvq-fv9f-wh4q
LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic
low1.3Feb 6, 2026CVE-2025-64529
SpiceDB WriteRelationships fails silently if payload is too big
low6.5Nov 13, 2025CVE-2025-49011
SpiceDB checks involving relations with caveats can result in no permission when permission is expected
low3.7Jun 6, 2025
