CVE-2020-5300

MEDIUMNVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
5.8
EG Score
5.8(medium)
EPSS
59.6%
KEV
Not listed

Published

April 6, 2020

Last Modified

November 21, 2024

References (6)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/ory/hydra—1.4.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:07 UTCEPSS rescore
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-07 13:43 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 02:21 UTCEPSS rescore
  8. 2026-07-06 02:21 UTCEPSS rescore
  9. 2026-07-05 02:28 UTCEPSS rescore
  10. 2026-07-05 02:28 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-04 06:29 UTCEPSS rescore
  13. 2026-07-02 16:57 UTCEPSS rescore
  14. 2026-07-02 03:17 UTCOSV refresh
  15. 2026-07-01 15:03 UTCEPSS rescore
  16. 2026-06-28 14:05 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-27 03:06 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-24 14:03 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 53 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 14:54 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-19 19:24 UTCEPSS rescore
  8. 2026-06-19 19:24 UTCEPSS rescore
  9. 2026-06-18 17:51 UTCEPSS rescore
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:46 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-14 05:43 UTCOSV refresh
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-13 22:58 UTCEPSS rescore
  18. 2026-06-12 23:10 UTCEPSS rescore
  19. 2026-06-12 23:10 UTCEPSS rescore
  20. 2026-06-11 13:58 UTCEPSS rescore
  21. 2026-06-11 13:58 UTCEPSS rescore
  22. 2026-06-10 22:16 UTCEPSS rescore
  23. 2026-06-10 13:20 UTCEPSS rescore
  24. 2026-06-08 14:15 UTCEPSS rescore
  25. 2026-06-07 15:23 UTCEPSS rescore
  26. 2026-06-07 15:23 UTCEPSS rescore
  27. 2026-06-06 13:46 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-05 22:45 UTCEPSS rescore
  31. 2026-06-05 22:45 UTCEPSS rescore
  32. 2026-06-05 06:08 UTCEPSS rescore
  33. 2026-06-05 06:08 UTCEPSS rescore
  34. 2026-06-04 13:10 UTCEPSS rescore
  35. 2026-06-04 13:10 UTCEPSS rescore
  36. 2026-06-02 20:11 UTCEPSS rescore
  37. 2026-06-02 20:11 UTCEPSS rescore
  38. 2026-06-01 13:50 UTCEPSS rescore
  39. 2026-05-31 22:29 UTCEPSS rescore
  40. 2026-05-31 22:29 UTCEPSS rescore
  41. 2026-05-31 00:15 UTCEPSS rescore
  42. 2026-05-31 00:15 UTCEPSS rescore
  43. 2026-05-29 13:42 UTCEPSS rescore
  44. 2026-05-28 13:43 UTCEPSS rescore
  45. 2026-05-28 13:43 UTCEPSS rescore
  46. 2026-05-27 13:39 UTCEPSS rescore
  47. 2026-05-27 13:39 UTCEPSS rescore
  48. 2026-05-27 05:34 UTCEG score recompute
  49. 2026-05-26 13:42 UTCEPSS rescore
  50. 2026-05-26 13:42 UTCEPSS rescore
  51. 2026-05-26 11:45 UTCOSV refresh
  52. 2026-05-26 07:17 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-5300?
CVE-2020-5300 is a medium vulnerability published on April 6, 2020. 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 'privatekeyjwt' [1], OpenId specification says the following about assertion jti: "A unique identifier for the token, which can be used to…
When was CVE-2020-5300 disclosed?
CVE-2020-5300 was first published in the National Vulnerability Database on April 6, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-5300 actively exploited?
CVE-2020-5300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-5300?
CVE-2020-5300 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2020-5300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-5300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-5300

Explore →

Is Your Infrastructure Affected by CVE-2020-5300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs