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

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-c38g-mx2c-9wf2, GO-2026-4800

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## 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 | Ecosystem | 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: Ory Keto.

## How do I fix CVE-2026-33505?

Upgrade github.com/ory/keto to 0.14.1-0.20260320140104-e4393662cd2e or later.

## Is CVE-2026-33505 being exploited?

There is no known exploitation of CVE-2026-33505 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33505 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-33505 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ory/keto (Go): affected all versions; fixed in 0.14.1-0.20260320140104-e4393662cd2e
- github.com/ory/keto (Go): affected all versions; fixed in 0.14.1-0.20260320140104-e4393662cd2e
- github.com/ory/keto (Go): affected all versions; fixed in 0.14.1-0.20260320140104-e4393662cd2e

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33505/ (Markdown: https://insights.sbomify.com/CVE-2026-33505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33505
- OSV: https://osv.dev/vulnerability/CVE-2026-33505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33505/
Summaries are generated and may contain mistakes; the official description above is the record.