Research / Finding
LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic F-AUTHZED-SPICEDB-001
Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic
Fixed in: spicedb v1.49.1
patched
details
Finding IDs F-AUTHZED-SPICEDB-001 GHSA GHSA-vhvq-fv9f-wh4q Status patched Fixed in spicedb v1.49.1 Upstream title LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic Upstream CWE CWE-248 Upstream publication 6 Feb 2026 Upstream updated 6 Feb 2026 Metadata fetched 23 Sep 2026 Upstream @1seal credit @1seal: reporter (accepted) F-AUTHZED-SPICEDB-001: Input / state handling. Untrusted cursor parsing reaches a MustParse panic. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-AUTHZED-SPICEDB-001
Security area (1seal assessment): Availability. Untrusted cursor parsing reaches a MustParse panic. Reviewed 24 Sep 2026.
Clarify or correct this record privately . The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy .
How this page groups evidence This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules .