# CVE-2026-33503: Ory Kratos has a SQL injection via forged pagination tokens

> Attackers can execute SQL injection via forged pagination tokens in Ory Kratos, especially if the default encryption secret is used.

- **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:** 1 Apr 2026
- **Also known as:** GHSA-hgx2-28f8-6g2r, GO-2026-4801

## What is CVE-2026-33503?

CVE-2026-33503 is a high-severity SQL injection vulnerability in ory kratos, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Ory Kratos is an identity, user management and authentication system for cloud services. Prior to version 26.2.0, 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. As a first line of defense, immediately configure a custom value for `secrets.pagination` by generating a cryptographically secure random secret. Next, upgrade Kratos** 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-33503?

3 open source packages ship an affected version, including github.com/ory/kratos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ory/kratos` | Go | All versions | 1.3.1-0.20260320110106-9d7085948039 |
| `github.com/ory/kratos` | Go | All versions | 1.3.1-0.20260320110106-9d7085948039 |
| `github.com/ory/kratos` | Go | All versions | 1.3.1-0.20260320110106-9d7085948039 |

Products: Ory Kratos.

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

Upgrade github.com/ory/kratos to 1.3.1-0.20260320110106-9d7085948039 or later.

## Is CVE-2026-33503 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33503 is a high-severity SQL injection vulnerability in ory kratos, 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-33503 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ory/kratos (Go): affected all versions; fixed in 1.3.1-0.20260320110106-9d7085948039
- github.com/ory/kratos (Go): affected all versions; fixed in 1.3.1-0.20260320110106-9d7085948039
- github.com/ory/kratos (Go): affected all versions; fixed in 1.3.1-0.20260320110106-9d7085948039

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-33503/ (Markdown: https://insights.sbomify.com/CVE-2026-33503/index.md)
```

## Sources

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

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