Advisory record · GHSA-c38g-mx2c-9wf2

Ory Keto has a SQL injection via forged pagination tokens

CVSS 7.2 HighEPSS 0.0023 · 14th percentile

Published by the GitHub Advisory Database at 20 Mar 2026, 20:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/ory/ketoGo<0.14.1-0.20260320140104-e4393662cd2e0.14.1-0.20260320140104-e4393662cd2e
Identifiers
GHSA-c38g-mx2c-9wf2 · CVE-2026-33505 · GO-2026-4800
Weakness (CWE)
CWE-89
Published
20 Mar 2026
Updated
27 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Ory Keto versions before 0.14.1-0.20260320140104-e4393662cd2e are vulnerable to SQL injection in the GetRelationships API through forged pagination tokens. An attacker who can reach the API and pass a raw pagination token can run arbitrary SQL queries, especially where secrets.pagination is unset, since Keto then uses a publicly known default encryption secret. Upgrade to 0.14.1-0.20260320140104-e4393662cd2e or later, and set a custom random value for secrets.pagination.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0023, the 14th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.