Permissions processing error in spacedb
Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-38361
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:37 UTC · Revision 1
Source evidence
Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue.
osv:CVE-2024-38361
Complete source record
{
"id": "8068317850dfbab5692ee58ac1a30bd109a9098a9dd5d1f1ab1ccef2bae398b0",
"url": "https://osv.dev/vulnerability/CVE-2024-38361",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Permissions processing error in spacedb",
"summary": "Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue.",
"evidence": "osv:CVE-2024-38361",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2024-38361",
"aliases": [
"CVE-2024-38361",
"GHSA-grjv-gjgr-66g2",
"GO-2024-2939"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/authzed/spicedb",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "684f85736ec85580f8ad45b654a30ecccccd36b8"
},
{
"fixed": "ecef31d2b266fde17eb2c3415e2ec4ceff96fbeb"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:authzed:spicedb:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.33.1"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "ecef31d2b266fde17eb2c3415e2ec4ceff96fbeb"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.33.0",
"v1.32.0",
"v1.31.0",
"v1.30.0",
"v1.29.1-rc1",
"v1.29.1",
"v1.29.0",
"v1.28.0-rc1",
"v1.28.0",
"v1.27.1-rc1",
"v1.27.0",
"v1.27.0-rc1",
"v1.26.0-rc2",
"v1.26.0",
"v1.26.0-rc1",
"v1.25.0",
"v1.25.0-rc4",
"v1.25.0-rc3",
"v1.25.0-rc2",
"v1.25.0-rc1",
"v1.24.0-rc3",
"v1.24.0",
"v1.24.0-rc2",
"v1.24.0-rc1",
"v1.23.1-rc1",
"v1.23.1",
"v1.23.0-rc4",
"v1.23.0",
"v1.23.0-rc3",
"v1.23.0-rc2",
"v1.23.0-rc1",
"v1.22.2",
"v1.22.1-rc1",
"v1.22.1",
"v1.22.0",
"v1.22.0-rc8",
"v1.22.0-rc7",
"v1.22.0-rc6",
"v1.22.0-rc5",
"v1.22.0-rc4",
"v1.22.0-rc2",
"v1.22.0-rc1",
"v1.21.0",
"v1.21.0-rc1",
"v1.19.0",
"v1.18.1",
"v1.17.0",
"v1.16.2",
"v1.16.1",
"v1.16.0",
"v1.15.0",
"v1.14.1",
"v1.14.0",
"v1.13.0",
"v1.12.0",
"v1.11.0",
"v1.10.0",
"v1.9.0",
"v1.8.0",
"v1.7.1",
"v1.7.0",
"v1.5.0",
"v1.4.0",
"v1.3.0",
"v1.2.0",
"v1.1.0",
"v1.0.0",
"v0.0.3",
"v0.0.2",
"v0.0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38361.json"
}
}
],
"modified": "2026-10-28T02:30:49.548870160Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38361.json",
"https://github.com/authzed/spicedb/security/advisories/GHSA-grjv-gjgr-66g2",
"https://nvd.nist.gov/vuln/detail/CVE-2024-38361",
"https://github.com/authzed/spicedb/commit/ecef31d2b266fde17eb2c3415e2ec4ceff96fbeb"
],
"provider_metadata": {
"cwe_ids": [
"CWE-281"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38361.json"
}
},
"related_cves": [
{
"value": "CVE-2024-38361",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517811,
"published_at": "2024-06-20T22:18:35.552+00:00"
}