CVE-2020-15222: Token reuse in Ory fosite

github.com/ory/fosite Updated 02 Oct 2025

Summary

24/05/2021
Yes i
High
8.1

CVE-2020-15222: Token reuse in Ory fosite. Affects github.com/ory/fosite versions < 0.31.0. Fixed in 0.31.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Ory fosite package is a Go library that provides OAuth2 and OpenID Connect server capabilities. It allows developers to implement authentication and authorization functionalities in their applications. This vulnerability affects versions prior to 0.31.0 of the package.

Vulnerability Detail

The vulnerability in Ory fosite arises when using the client authentication method 'private_key_jwt'. According to the OpenID specification, the 'jti' assertion in the token should be a unique identifier to prevent token reuse. However, Hydra, which is built on top of Ory fosite, does not enforce the uniqueness of this 'jti' value. As a result, an attacker can send the same token request multiple times, obtaining multiple access tokens. This can lead to unauthorized access and potential security breaches.

How To Fix

Latest published version: v0.49.0 as of 23 Oct 2026

go get github.com/ory/fosite@v0.49.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.31.0

This is the first release that contains the fix.

go get github.com/ory/fosite@v0.31.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating the package is not immediately feasible, a workaround is to disallow clients from using the 'private_key_jwt' authentication method. This can be achieved by configuring the application to only allow other supported authentication methods.

Conclusion

The vulnerability in Ory fosite allows for token reuse when using the 'private_key_jwt' authentication method. This can lead to unauthorized access and potential security breaches. It is crucial to update the package to version 0.31.0 or later to fix the issue. If immediate update is not possible, disallowing the use of 'private_key_jwt' can serve as a temporary workaround. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for github.com/ory/fosite →

Share this vulnerability

FAQ

Ory fosite is a Go library that provides OAuth2 and OpenID Connect server capabilities for implementing authentication and authorization in applications.

The vulnerability allows an attacker to reuse tokens obtained through the 'private_key_jwt' authentication method, potentially leading to unauthorized access and security breaches.

To fix this vulnerability, update the Ory fosite package to version 0.31.0 or later. Rebuild your application after updating the dependencies.

Yes, you can disallow clients from using the 'private_key_jwt' authentication method as a temporary workaround until the package is updated.

There is no known exploit available at the moment, but it is recommended to apply the fix as soon as possible to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/ory/fosite.

How To Fix

Latest published version: v0.49.0 as of 23 Oct 2026

go get github.com/ory/fosite@v0.49.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.31.0

This is the first release that contains the fix.

go get github.com/ory/fosite@v0.31.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback