Improper Authorization Affecting ruby-doorkeeper-openid-connect package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN13-RUBYDOORKEEPEROPENIDCONNECT-19272334
- published27 Aug 2026
- disclosed25 Aug 2026
Introduced: 25 Aug 2026
NewCVE-2026-70665 (opens in a new tab)How to fix?
There is no fixed version for Debian:13 ruby-doorkeeper-openid-connect.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ruby-doorkeeper-openid-connect package and not the ruby-doorkeeper-openid-connect package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
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 scope set. Under certain conditions, this allows a self-registered client to obtain scopes beyond what the server intended to grant. In DynamicClientRegistrationController#application_params, the scopes attribute is assigned directly from params[:scope] with no validation against Doorkeeper.configuration.scopes or optional_scopes. Combined with enforce_configured_scopes being off by default and Doorkeeper's ScopeChecker prioritizing application-level scopes over server-level scopes, this creates a privilege escalation path. This issue is fixed in version 1.10.4.