← Back
CVE-2026-46668
Vulnerability in github.com/authzed/spicedb (CVE-2026-46668)
Summary
vulnerability in github.com/authzed/spicedb (CVE-2026-46668). Risk of unauthorized operations or information disclosure. Exploitable via ``lr3``. Mitigation: upgrade to `1.52.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46668** has been found in github.com/authzed/spicedb.
Attackers can target a specific entry point like ``lr3`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/authzed/spicedb to **1.52.0** or later.
If unsure, ask your IT team or search "github.com/authzed/spicedb CVE-2026-46668" on the vendor's site.
CVE-2026-46668 (github.com/authzed/spicedb) — CWE-285 /
Attack surface: `lr3` / `LookupResources` / `CheckBulk` / `caveat`
Patched: `1.52.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-285) exists in github.com/authzed/spicedb. Attackers reach the vulnerable code path via ``lr3`` without authentication.
📍 Affected scope
github.com/authzed/spicedb — . Attack surface: `lr3` / `LookupResources` / `CheckBulk` / `caveat`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.52.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/authzed/spicedb' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/authzed/spicedb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/authzed/spicedb` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/authzed/spicedb to 1.52.0ステージング環境で 1.52.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/authzed/spicedb
[{"type":"SEMVER","events":[{"introduced":"1.15.0"},{"fixed":"1.52.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-46668
- package https://github.com/authzed/spicedb
- web https://github.com/authzed/spicedb/security/advisories/GHSA-mqcf-gqvg-rmhm
- web https://github.com/authzed/spicedb/pull/3065
- web https://github.com/advisories/GHSA-mqcf-gqvg-rmhm
- web https://github.com/authzed/spicedb/releases/tag/v1.52.0