How many CVEs have patched checkRequestToKey?

1 published CVEs changed checkRequestToKey in authzed/spicedb, in 1 distinct patches totalling 20 changed lines, between 2026 and 2026.

What is the latest CVE that changed checkRequestToKey?

CVE-2026-55866 (SpiceDBChecks involving relations with caveats can result in unconditional permission when conditional permission is expected), published 2026-09-14, changed lines 42 to 72 of internal/dispatch/keys/computed.go.

How does checkRequestToKey compare to the rest of authzed/spicedb?

authzed/spicedb has 14 CVEs with a located fix in total; 1 of them changed checkRequestToKey.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

authzed/spicedb

Function

checkRequestToKey

Name: checkRequestToKey in authzed/spicedb: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

internal/dispatch/keys/computed.go

Last patched September 14, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

20

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

checkRequestToKey in authzed/spicedb was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 20 lines in total.

authzed/spicedb has 14 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed checkRequestToKey, newest first, with the lines each fix touched.

SpiceDBChecks involving relations with caveats can result in unconditional permission when conditional permission is expected
CVE-2026-55866 · lines 42–72 · +16 −4
Low · CVSS 3.7
EPSS 0.3%2026-09-14

Get an alert when the next CVE fix lands in authzed/spicedb, with the patched functions.

Monitor spicedb CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1lookupResourcesRequest2ToKeyinternal/dispatch/keys/computed.go1 CVEs · 1 patches2026

Other hotspots in the repository

Functions in authzed/spicedb changed by the most CVE fixes.

lookupResourcesRequest2ToKey1 CVEs · internal/dispatch/keys/computed.go computeCallHash1 CVEs · internal/services/v1/hash.go LookupResources2DispatchKey1 CVEs · internal/dispatch/keys/keys.go LookupResources2CacheKey1 CVEs · internal/dispatch/keys/keys.go buildArrowIterators1 CVEs · pkg/query/build_tree.go buildIntersectionArrowIterators1 CVEs · pkg/query/build_tree.go

All patched functions in authzed/spicedb

Frequently asked questions

Common questions about CVE fixes to checkRequestToKey.

How many CVEs have patched checkRequestToKey?: 1 published CVEs changed checkRequestToKey in authzed/spicedb, in 1 distinct patches totalling 20 changed lines, between 2026 and 2026.
What is the latest CVE that changed checkRequestToKey?: CVE-2026-55866 (SpiceDBChecks involving relations with caveats can result in unconditional permission when conditional permission is expected), published 2026-09-14, changed lines 42 to 72 of internal/dispatch/keys/computed.go.
How does checkRequestToKey compare to the rest of authzed/spicedb?: authzed/spicedb has 14 CVEs with a located fix in total; 1 of them changed checkRequestToKey.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track authzed/spicedb CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing