Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Ory Hydra versions before 1.4.0 do not check that the jti value in a private_key_jwt client assertion is unique, so the same assertion can be reused. An attacker who has captured a valid assertion could replay it to obtain additional access tokens within the assertion's short expiry window. Upgrade to 1.4.0 or later. Until then, disallow private_key_jwt for clients or use short assertion expiry times.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.8 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.010, the 64th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-3p3g-vpw6-4w66
- OSV: GHSA-3p3g-vpw6-4w66
- github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66
- nvd.nist.gov/vuln/detail/CVE-2020-5300
- github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3
- github.com/ory/hydra
- github.com/ory/hydra/releases/tag/v1.4.0
- openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication