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.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
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 | 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 include Ory Hydra.
How do I fix CVE-2026-33504?
Upgrade to a fixed version.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
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
Sources
Also known as GHSA-r9w3-57w2-gch2, GO-2026-4807.