Improper Authentication 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-DEBIAN11-RUBYDOORKEEPEROPENIDCONNECT-19272322
- published27 Aug 2026
- disclosed25 Aug 2026
Introduced: 25 Aug 2026
NewCVE-2026-44476 (opens in a new tab)How to fix?
There is no fixed version for Debian:11 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:11 relevant fixed versions and status.
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 client_secret. This occurs because the Dynamic Client Registration feature creates applications with confidential: false hard-coded, even though the registration response returns a client_secret and advertises support for the client_secret_basic and client_secret_post authentication methods; since Doorkeeper treats a blank or missing secret as valid for non-confidential (public) clients, the secret is never verified. Only projects that have explicitly enabled Dynamic Client Registration, which is disabled by default, are affected. This issue is fixed in version 1.10.0.