Ory Keto has a SQL injection via forged pagination tokens

Summary

Ory Keto is am open source authorization server for managing permissions at scale. Prior to version 26.2.0, the GetRelationships API in Ory Keto is vulnerable to SQL injection due to flaws in its pagination implementation. Pagination tokens are encrypted using the secret configured in `secrets.pagination`. An attacker who knows this secret can craft their own tokens, including malicious tokens that lead to SQL injection. If this configuration value is not set, Keto falls back to a hard-coded default pagination encryption secret. Because this default value is publicly known, attackers can generate valid and malicious pagination tokens manually for installations where this secret is not set. This issue can be exploited when GetRelationships API is directly or indirectly accessible to the attacker, the attacker can pass a raw pagination token to the affected API, and the configuration value `secrets.pagination` is not set or known to the attacker. An attacker can execute arbitrary SQL queries through forged pagination tokens. As a first line of defense, immediately configure a custom value for `secrets.pagination` by generating a cryptographically secure random secret. Next, upgrade Keto to a fixed version, 26.2.0 or later, as soon as possible.

Timeline

1. Mar 26, 2026, 6:37 PM UTCCVE published
2. Mar 30, 2026, 1:57 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Mar 30, 2026, 2:55 PM UTCRecord last updated

Affected versions

• ory keto

  fixed in 26.2.0

• github.com/ory/ketoGo

  fixed in 0.14.1-0.20260320140104-e4393662cd2e

References 1