Answer in brief
CVE-2026-44476 records a Medium severity (CVSS 6.3) vulnerability in Doorkeeper OpenID Connect: Dynamic Client Registration feature creates public clients with client_secret. The current sources do not mark it as known exploited. The current feed maps doorkeeper-gem/doorkeeper-openid_connect (generic), doorkeeper-openid_connect (rubygems), doorkeeper-openid_connect (rubygems). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps doorkeeper-gem/doorkeeper-openid_connect (generic), doorkeeper-openid_connect (rubygems), doorkeeper-openid_connect (rubygems). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| doorkeeper-gem/doorkeeper-openid_connectgeneric | >= 1.9.0, < 1.10.0 | Not reported |
| doorkeeper-openid_connectrubygems | =1.9.0 | 1.10.0 |
| doorkeeper-openid_connectrubygems | >=1.9.0 <1.10.0 | 1.10.0 |
Published upstream
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.