Approved changes feed: RSS · Atom

cpe:2.3:a:ory:hydra:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorOry (2936b801-e543-5a0e-bb3b-f36ae09a3b16)
ProductHydra (67f8e707-9108-5fae-82ee-26d2fe63fbd5)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/ory/hydra purl2cpe 2026-06-01 10:12:23.788126

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-33504 vulnerable 2026-06-08 07:59:10.216079 Ory Hydra has a SQL injection via forged pagination tokens
HIGH (7.2)
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.
Published: 2026-03-26T17:38:10.809Z
Updated: 2026-03-26T18:46:01.194Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-5300 vulnerable 2026-06-08 05:26:41.689445 Disallow replay of `private_key_jwt` by blacklisting JTIs in Hydra
MEDIUM (5.8)
In Hydra (an OAuth2 Server and OpenID Certified™ OpenID Connect Provider written in Go), before version 1.4.0+oryOS.17, when using client authentication method 'private_key_jwt' [1], OpenId specification says the following about assertion `jti`: "A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties". Hydra does not check the uniqueness of this `jti` value. Exploiting this vulnerability is somewhat difficult because: - TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks - The expiry time of the JWT gives only a short window of opportunity where it could be replayed This has been patched in version v1.4.0+oryOS.17
Published: 2020-04-06T16:30:14.000Z
Updated: 2024-08-04T08:22:09.093Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.