dbcve.org
KetoApplication · Ory

CVE-2026-33505

HIGH · 7.2 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 26.2.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Ory Keto versions before 26.2.0 contain a SQL injection vulnerability in the GetRelationships API's pagination implementation. Attackers can forge pagination tokens using the default hard-coded secret (when `secrets.pagination` is not configured) or a known custom secret, allowing arbitrary SQL query execution.

MitigationUpgrade Ory Keto to version 26.2.0 or later and configure a cryptographically secure random value for `secrets.pagination` to prevent token forgery.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KetoApplication
Affected:< 26.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed Ory Keto version
    Run 'keto version' or check the running container image tag to identify the version number
    Affected if The version is below 26.2.0
  2. Locate the Ory Keto configuration file
    Find the keto.yml or keto.yaml configuration file used by your deployment, typically in /etc/keto/ or the working directory
    Affected if The configuration file exists and is in use
  3. Verify if secrets.pagination is configured
    Inspect the configuration file and check for the 'secrets.pagination' setting under the serve or general section
    Affected if The secrets.pagination setting is missing or uses a default value rather than a custom cryptographically secure secret
  4. Confirm GetRelationships API exposure
    Determine if the GetRelationships API endpoint is accessible to untrusted users or networks
    Affected if The GetRelationships API is exposed without authentication or to external consumers
  5. Review API access logs for pagination tokens
    Examine API access logs for requests to the GetRelationships endpoint that include pagination tokens
    Affected if Pagination tokens are being used in API requests and the version is vulnerable

You are affected if Ory Keto version is below 26.2.0 AND the GetRelationships API is accessible AND secrets.pagination is either unset or uses a known/default value.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 26.2.0 or later
Fixed in 26.2.0
Interim mitigation

Upgrade Ory Keto to version 26.2.0 or later and configure a cryptographically secure random value for `secrets.pagination` to prevent token forgery.

Recommended fix High confidence

26.2.0 or later

  1. Generate a cryptographically secure random secret and configure it as the `secrets.pagination` value in your Keto configuration
  2. Upgrade Keto to version 26.2.0 or later
Caveat Review the release notes for version 26.2.0 to check for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Keto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33505 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33505 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data