Ory Hydra has a SQL injection via forged pagination tokens

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-33504: 0.36% estimated exploitation activity in the next 30 days; percentile 30.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description Following Admin APIs in Ory Hydra are vulnerable to SQL injection due to flaws in its pagination implementation: - listOAuth2Clients - listOAuth2ConsentSessions - listTrustedOAuth2JwtGrantIssuers 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. Preconditions This issue can be exploited when the following conditions are met: - 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 - 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 Impact An attacker can execute arbitrary SQL queries through forged pagination tokens. Mitigation As a first line of defense,…

Published by the source

20 Mar 2026, 20:55 UTC

Last modified by the source

27 Mar 2026, 20:59 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r9w3-57w2-gch2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33504

Advisory: Ory Hydra has a SQL injection via forged pagination tokens
IDs: CVE-2026-33504, GHSA-r9w3-57w2-gch2
Record: https://patchnext.com/advisories/cve-2026-33504 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/ory/hydra/v2 2.3.1-0.20260320110106-0b84568fffcc. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ory/hydra/v2: affected < 2.3.1-0.20260320110106-0b84568fffcc; fixed in 2.3.1-0.20260320110106-0b84568fffcc
- Go github.com/ory/hydra: affected <= 1.11.10

## Suggested inspection (read-only)
- Go github.com/ory/hydra/v2: check the installed version with your package manager.
- Go github.com/ory/hydra: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ory/hydra/v2, github.com/ory/hydra.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r9w3-57w2-gch2 (GitHub-reviewed advisory GHSA-r9w3-57w2-gch2 lists affected ranges: Go github.com/ory/hydra >=0 =0 <2.3.1-0.20260320110106-0b84568fffcc)

Commands are suggestions: review each one before running it.