Is github.com/authzed/spicedb 1.53 vulnerable?

Go · 1 release from 1.53.0 to 1.53.0 · latest github.com/authzed/spicedb is 1.57.1 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/authzed/spicedb 1.53.0, the last 1.53 release, is affected by 2 known security advisories (2 low), including CVE-2026-55866, CVE-2026-55866. Upgrade to 1.54.0 or later to fix all of them.

Upgrade with:go get github.com/authzed/spicedb@v1.54.0

Is your project on an affected github.com/authzed/spicedb?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/authzed/spicedb 1.53.0

  • LowCVE-2026-55866GO-2026-513325 Jun 2026

    SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected in github.com/authzed/spicedb

    Affected
    >=1.34.0 <1.54.0
    Fixed in
    1.54.0
  • LowCVE-2026-55866GHSA-4vrg-r928-h5vv19 Jun 2026

    SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected

    Affected
    >=1.34.0 <1.54.0
    Fixed in
    1.54.0

Which of your client projects are still on github.com/authzed/spicedb 1.53?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/authzed/spicedb version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/authzed/spicedb versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.