Ory Kratos has a SQL injection via forged pagination tokens

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-33503: 0.26% estimated exploitation activity in the next 30 days; percentile 18.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description The ListCourierMessages Admin API in Ory Kratos 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, Kratos falls back to a 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 the following conditions are met: - ListCourierMessages 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 tokens.…

Published by the source

20 Mar 2026, 20:54 UTC

Last modified by the source

27 Mar 2026, 20:59 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hgx2-28f8-6g2r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33503

Advisory: Ory Kratos has a SQL injection via forged pagination tokens
IDs: CVE-2026-33503, GHSA-hgx2-28f8-6g2r
Record: https://patchnext.com/advisories/cve-2026-33503 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ory/kratos 1.3.1-0.20260320110106-9d7085948039. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ory/kratos: affected < 1.3.1-0.20260320110106-9d7085948039; fixed in 1.3.1-0.20260320110106-9d7085948039

## Suggested inspection (read-only)
- Go github.com/ory/kratos: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ory/kratos.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hgx2-28f8-6g2r (GitHub-reviewed advisory GHSA-hgx2-28f8-6g2r lists affected ranges: Go github.com/ory/kratos >=0 <1.3.1-0.20260320110106-9d7085948039)

Commands are suggestions: review each one before running it.