← Back
CVE-2026-40091
Vulnerability in github.com/authzed/spicedb (CVE-2026-40091)
Summary
vulnerability in github.com/authzed/spicedb (CVE-2026-40091). Confidential information can be exposed externally. Exploitable via ``info``. Mitigation: upgrade to `1.51.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40091** has been found in github.com/authzed/spicedb.
Attackers can target a specific entry point like ``info`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade github.com/authzed/spicedb to **1.51.1** or later.
If unsure, ask your IT team or search "github.com/authzed/spicedb CVE-2026-40091" on the vendor's site.
CVE-2026-40091 (github.com/authzed/spicedb) — CWE-532 /
Attack vector: local / no user interaction
Attack surface: `info` / `DatastoreConfig.URI` / `warn` / `error`
Patched: `1.51.1` — apply immediately
Workaround: Change the log level to `warn` or `error`.
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-532) exists in github.com/authzed/spicedb. Attackers reach the vulnerable code path via ``info`` without authentication.
📍 Affected scope
github.com/authzed/spicedb — . Attack surface: `info` / `DatastoreConfig.URI` / `warn` / `error`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.51.1**.
🛡️ Workaround
Workaround: Change the log level to `warn` or `error`.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Change the log level to `warn` or `error`.パッチが適用されるまでの応急処置として、Change the log level to `warn` or `error`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/authzed/spicedb to 1.51.1ステージング環境で 1.51.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.49.0"},{"fixed":"1.51.1"}]}]