CVE-2026-44476
CVE-2026-44476 · Doorkeeper OpenID Connect: Dynamic Client Registration feature creates public clients with client_secret
CVSS 6.3 · Medium · EPSS 0.6% · Fix available
Compare with your installed version
Affected products and known fixed versions are public information. Compare them with your installed version.
- doorkeeper-openid_connectNo fix published
- ruby-doorkeeper-openid-connect Debian 12No fix published
- ruby-doorkeeper-openid-connect Debian 13No fix published
- ruby-doorkeeper-openid-connect Debian 14Update to 1.10.1-1
- and 6 more
Check the installed version:
dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="ruby-doorkeeper-openid-connect"'Assess your server’s risks
The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.
Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.
curl -fsSL https://patchfirst.dev/check.sh | shChannels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
- Published
- Updated
Affected products and versions
doorkeeper-openid_connect
- Versions
- >= 1.9.0, < 1.10.0: Affected
No fix published
ruby-doorkeeper-openid-connect Debian 12
- Versions
- 1.10.1-1
- 1.10.5-1
- 1.8.0-1
- 1.8.11-1
- 1.8.11-2
- 1.8.5-1
All versions (9)
- 1.8.5-2
- 1.8.7-1
- 1.9.0-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-doorkeeper-openid-connect Debian 13
- Versions
- 1.10.1-1
- 1.10.5-1
- 1.8.11-1
- 1.8.11-2
- 1.8.7-1
- 1.9.0-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-doorkeeper-openid-connect Debian 14
- Versions
- 1.8.11-1
- 1.8.11-2
- 1.8.7-1
- 1.9.0-1
- Affected ranges
- ECOSYSTEM: < 1.10.1-1
Update to 1.10.1-1
doorkeeper-openid_connect RubyGems
- Versions
- 1.9.0
- Affected ranges
- ECOSYSTEM: ≥ 1.9.0, < 1.10.0
Update to 1.10.0
ruby-doorkeeper-openid-connect Ubuntu 18.04 LTS
- Versions
- 1.1.2-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-doorkeeper-openid-connect Ubuntu 20.04 LTS
- Versions
- 1.5.5-1
- 1.6.3-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-doorkeeper-openid-connect Ubuntu 22.04 LTS
- Versions
- 1.7.4-2
- 1.8.0-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-doorkeeper-openid-connect Ubuntu 24.04 LTS
- Versions
- 1.8.7-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-doorkeeper-openid-connect Ubuntu 26.04 LTS
- Versions
- 1.8.7-1
- 1.8.11-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published