CVE-2026-70665
CVE-2026-70665 · Doorkeeper OpenID Connect: DCR endpoint persists unvalidated client-supplied scopes
CVSS 4.2 · Medium · EPSS 0.3% · 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.5-1
- and 5 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 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.
- Published
- Updated
Stack: system
Affected products and versions
doorkeeper-openid_connect
- Versions
- < 1.10.4: 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.10.1-1
- 1.8.11-1
- 1.8.11-2
- 1.8.7-1
- 1.9.0-1
- Affected ranges
- ECOSYSTEM: < 1.10.5-1
Update to 1.10.5-1
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