← back
CVE-2026-33505

Ory Keto has a SQL injection via forged pagination tokens

CVSS 7.2 HIGHEPSS 0.2%CWE-89
In short

Ory Keto's GetRelationships API can be exploited through crafted pagination tokens to execute arbitrary SQL commands. This happens because pagination tokens use a default encryption secret that is publicly known, allowing attackers to forge malicious tokens if a custom secret is not configured.

Technical detail

SQL injection vulnerability in GetRelationships API pagination token handling (CWE-89). Attack vector requires knowledge of the pagination encryption secret (hardcoded default or configured value) to craft malicious tokens; attacker must have access to the affected API endpoint. Impact allows execution of arbitrary SQL queries, potentially compromising data confidentiality and integrity.

Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Affected products
ory · keto

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →