doorkeeper-gem doorkeeper-openid_connect up to 1.9.x Dynamic Client Registration improper authentication

Summaryinfo

A vulnerability described as critical has been identified in doorkeeper-gem doorkeeper-openid_connect up to 1.9.x. This vulnerability affects unknown code of the component Dynamic Client Registration. The manipulation results in improper authentication. This vulnerability is reported as CVE-2026-44476. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical has been found in doorkeeper-gem doorkeeper-openid_connect up to 1.9.x. Affected is an unknown code block of the component Dynamic Client Registration. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-44476 since 05/06/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.

Upgrading to version 1.10.0 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• doorkeeper-gem

Name

• doorkeeper-openid_connect

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9

Website

• Product: https://github.com/doorkeeper-gem/doorkeeper-openid_connect/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion