GHSA-vhvq-fv9f-wh4q: LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic
Description A malformed or tampered-with LookupResources Cursor token can cause a panic in the SpiceDB process if it fails to parse. If an attacker were able to make requests to a SpiceDB instance, they could affect its availability.
Published Feb 6, 2026
Affected packages
github.com/authzed/spicedb
- Ecosystem
- Go
- Affected
- >= 1.29.3, < 1.49.1
- Fixed in
- 1.49.1
- Check
go list -m github.com/authzed/spicedb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Description
A malformed or tampered-with LookupResources Cursor token can cause a panic in the SpiceDB process if it fails to parse. If an attacker were able to make requests to a SpiceDB instance, they could affect its availability.
Reproduction
If one was to take a cursor from a LookupResources call, decode it according to the logic that SpiceDB uses, and modify the Sections field to include an invalid relationship string, the process will panic.
Impact
An attacker would need both the ability to create a gRPC connection to your SpiceDB instance and a valid token, or else the ability to pass a cursor token from outside your application through to your SpiceDB instance.
If an attacker had this ability, they could bring down SpiceDB instances, reducing the availability of SpiceDB and any service that depends on it.
Mechanism
The SpiceDB process does not validate the contents of this Sections component of the Cursor message. In affected versions, it uses a parsing function that calls panic if the value cannot be parsed as a relationship.
Fix
This issue was fixed in https://github.com/authzed/spicedb/pull/2878.
Remediations
- Prevent client control of the
optional_cursorfield inLookupResourcescalls - Upgrade to an unaffected version
Credited to 1seal.
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, 2026CVE-2025-65111
SpiceDB: LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results
low2.9Nov 21, 2025CVE-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
