Doorkeeper is an OAuth 2 provider for Ruby on Rails. In version 1.9.0, an attacker who knows only a dynamically registered client's client_id, which is public information, can authenticate as that client at the token endpoint and obtain an access token without providing its clien...
Product
debian/ruby-doorkeeper-openid-connect vulnerabilities
3 published CVES affecting debian/ruby-doorkeeper-openid-connect, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 0
- High
- 0
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest debian/ruby-doorkeeper-openid-connect CVEs
Newest publication first
-
MediumCVSS 6.3 EPSS 0.56% PoC
-
CVE-2026-70665 Doorkeeper OpenID Connect: DCR endpoint persists unvalidated client-supplied scopes
PublishedMediumCVSS 4.2 EPSS 0.26%Doorkeeper OpenID Connect implements an OpenID Connect authentication provider for Rails applications on top of Doorkeeper. Prior to 1.10.4, the Dynamic Client Registration (DCR) endpoint persists client-supplied scopes without validating them against the server's configured scop...
-
MediumCVSS 6.1 EPSS 1.3%
Doorkeeper::OpenidConnect (aka the OpenID Connect extension for Doorkeeper) 1.4.x and 1.5.x before 1.5.4 has an open redirect via the redirect_uri field in an OAuth authorization request (that results in an error response) with the 'openid' scope and a prompt=none value. This all...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.