CVE-2026-33505 Ory Keto has a SQL injection via forged pagination tokens
Attackers can execute arbitrary SQL queries via forged pagination tokens in Ory Keto if the default encryption secret is used or known.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-33505?
CVE-2026-33505 is a high-severity SQL injection vulnerability in ory keto, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
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.
Weakness: CWE-89
Which versions are affected by CVE-2026-33505?
3 open source packages ship an affected version, including github.com/ory/keto. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/ory/keto Go | All versions | 0.14.1-0.20260320140104-e4393662cd2e |
github.com/ory/keto Go | All versions | 0.14.1-0.20260320140104-e4393662cd2e |
github.com/ory/keto Go | All versions | 0.14.1-0.20260320140104-e4393662cd2e |
Products include Ory Keto.
How do I fix CVE-2026-33505?
Upgrade github.com/ory/keto to 0.14.1-0.20260320140104-e4393662cd2e or later.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-33505 being exploited?
There is no known exploitation of CVE-2026-33505 in the wild and no public exploit code.
Sources
Also known as GHSA-c38g-mx2c-9wf2, GO-2026-4800.