# CVE-2026-33504: Ory Hydra has a SQL injection via forged pagination tokens

> Attackers with knowledge of pagination secrets can inject SQL via forged tokens in Ory Hydra admin APIs, requiring secret configuration and upgrade.

- **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:** 26 Mar 2026
- **Also known as:** GHSA-r9w3-57w2-gch2, GO-2026-4807

## What is CVE-2026-33504?

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

### Official description

Ory Hydra is an OAuth 2.0 Server and OpenID Connect Provider. Prior to version 26.2.0, the listOAuth2Clients, listOAuth2ConsentSessions, and listTrustedOAuth2JwtGrantIssuers Admin APIs in Ory Hydra are vulnerable to SQL injection due to flaws in its pagination implementation. Pagination tokens are encrypted using the secret configured in `secrets.pagination`. If this value is not set, Hydra falls back to using `secrets.system`. An attacker who knows this secret can craft their own tokens, including malicious tokens that lead to SQL injection. This issue can be exploited when one or more admin APIs listed above are 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 set and known to the attacker, or `secrets.pagination` is not set and `secrets.system` is 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 Hydra to the fixed version, 26.2.0 as soon as possible.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-33504?

6 open source packages ship an affected version, including github.com/ory/hydra and github.com/ory/hydra/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ory/hydra` | Go | All versions | None |
| `github.com/ory/hydra` | Go | All versions to 1.11.10 | None |
| `github.com/ory/hydra` | Go | All versions to 1.11.10 | None |
| `github.com/ory/hydra/v2` | Go | All versions | 2.3.1-0.20260320110106-0b84568fffcc |
| `github.com/ory/hydra/v2` | Go | All versions | 2.3.1-0.20260320110106-0b84568fffcc |
| `github.com/ory/hydra/v2` | Go | All versions | 2.3.1-0.20260320110106-0b84568fffcc |

Products: Ory Hydra.

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

Upgrade to a fixed version.

## Is CVE-2026-33504 being exploited?

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

## Other vulnerabilities in ory hydra

- [CVE-2019-8400](https://insights.sbomify.com/CVE-2019-8400/): Hydra has Reflected XSS via error_hint parameter (medium 6.1)
- [CVE-2020-5300](https://insights.sbomify.com/CVE-2020-5300/): Disallow replay of `private_key_jwt` by blacklisting JTIs in Hydra (medium 5.8)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- github.com/ory/hydra (Go): affected all versions; no fix listed
- github.com/ory/hydra (Go): affected all versions up to 1.11.10; no fix listed
- github.com/ory/hydra (Go): affected all versions up to 1.11.10; no fix listed
- github.com/ory/hydra/v2 (Go): affected all versions; fixed in 2.3.1-0.20260320110106-0b84568fffcc
- github.com/ory/hydra/v2 (Go): affected all versions; fixed in 2.3.1-0.20260320110106-0b84568fffcc
- github.com/ory/hydra/v2 (Go): affected all versions; fixed in 2.3.1-0.20260320110106-0b84568fffcc

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

## Sources

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

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