# Ory Kratos has a SQL injection via forged pagination tokens

Advisory record · `GHSA-hgx2-28f8-6g2r`

- **Identifiers:** `GHSA-hgx2-28f8-6g2r` · `CVE-2026-33503` · `GO-2026-4801`
- **State:** Confirmed
- **Severity:** CVSS 7.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 20 Mar 2026
- **Updated:** 27 Mar 2026
- **Reviewed by a person:** No

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

## Affected packages

- `github.com/ory/kratos` (Go): affected `<1.3.1-0.20260320110106-9d7085948039`; fixed in `1.3.1-0.20260320110106-9d7085948039`

## Machine-written summary

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

> Ory Kratos (github.com/ory/kratos) versions before 1.3.1-0.20260320110106-9d7085948039 are vulnerable to SQL injection in the ListCourierMessages Admin API via forged pagination tokens. An attacker who can reach that API and submit a pagination token can run arbitrary SQL, particularly where secrets.pagination is unset, since Kratos then uses a publicly known default secret. Upgrade to 1.3.1-0.20260320110106-9d7085948039 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

- 7.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hgx2-28f8-6g2r)

## Sources

- [GitHub Advisory Database: GHSA-hgx2-28f8-6g2r](https://github.com/advisories/GHSA-hgx2-28f8-6g2r)
- [OSV: GHSA-hgx2-28f8-6g2r](https://osv.dev/vulnerability/GHSA-hgx2-28f8-6g2r)
- <https://github.com/ory/kratos/security/advisories/GHSA-hgx2-28f8-6g2r>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33503>
- <https://github.com/ory/kratos>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hgx2-28f8-6g2r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hgx2-28f8-6g2r/>. Everything for agents: <https://agentprime.io/llms.txt>.
