Skip to content

← Public intelligence

Go package

github.com/ory/keto

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.2GoPublished

    Ory Keto has a SQL injection via forged pagination tokens

    CVE-2026-33505 · GHSA-c38g-mx2c-9wf2

    Affected
    • Go github.com/ory/keto < 0.14.1-0.20260320140104-e4393662cd2e
    Fixed in
    0.14.1-0.20260320140104-e4393662cd2e· Vendor fix available
    Issue
    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. Preconditions This issue can be exploited when all of the following conditions are met: - GetRelationships API is directly or indirectly accessible to the attacker - The attacker can pass a raw pagination token to the affected API - The configuration value secrets.pagination is not set or known to the attacker Impact An attacker can execute arbitrary SQL queries through forged pagination…

    Recommended action: Upgrade to 0.14.1-0.20260320140104-e4393662cd2e (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →