CVE-2026-44476 MEDIUM

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

Vendor Doorkeeper-Gem
Product doorkeeper-openid_connect
Weakness CWE-287 · Improper authentication
Published August 25, 2026
Last update August 26, 2026

CVSS base score

6.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality
Integrity

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

What the vulnerability does

01Description

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.

Key dates

02Disclosure timeline

August 25, 2026 CVE published
August 26, 2026 Record updated

Related vulnerabilities

04Related CVE