NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · RubyGems

CVE-2026-44476: Doorkeeper Openid Connect: Dynamic Client Registration feature creates public clients with client_secret

mediumCVSS 4.0 6.3GHSA-m6vc-f87m-cc2h

Impact The DynamicClientRegistrationController#register action hard-codes confidential: false when creating applications (dynamicclientregistrationcontroller.rb:18-25), yet the response includes a clientsecret and advertises tokenendpointauthmethodssupported: ["clientsecretbasic", "clientsecretpost"].

Published Jun 4, 2026 · Updated Jun 9, 2026

Affected packages

doorkeeper-openid_connect

Ecosystem
RubyGems
Affected
= 1.9.0
Fixed in
1.10.0
Check
bundle info doorkeeper-openid_connect

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The DynamicClientRegistrationController#register action hard-codes confidential: false when creating applications (dynamic_client_registration_controller.rb:18-25), yet the response includes a client_secret and advertises token_endpoint_auth_methods_supported: ["client_secret_basic", "client_secret_post"].

Because Doorkeeper's Application.by_uid_and_secret treats a blank/missing secret as valid for non-confidential (public) clients, an attacker who knows only the client_id (which is public information) can authenticate as the dynamically-registered client at the token endpoint.

Note that Dynamic Client Registration is opt-in feature which is disabled by default so only projects that explicitly enabled it are affected.

Steps to Reproduce

  1. Enable dynamic client registration in the initializer
  2. POST /oauth/registration with client_name, redirect_uris, and scope
  3. Observe: response returns client_secret, but the created

Doorkeeper::Application has confidential: false

  1. Call Doorkeeper::Application.by_uid_and_secret(client_id, nil) — it

returns the application (credentials bypass)

  1. POST /oauth/token with grant_type=client_credentials and only

client_id (no client_secret) — the token endpoint issues an access token without any secret verification

Patches

Patched in 1.10.0

Workarounds

Upgrade existing applications created with a Dynamic Client registration to have confidential: true

Credited to 55728.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology