Improper Authentication Affecting commercial-gitlab-rails-ee-19.3 package, versions <19.3.3-r4


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.56% (45th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-COMMERCIALGITLABRAILSEE193-20825172
  • published11 Oct 2026
  • disclosed25 Aug 2026

Introduced: 25 Aug 2026

CVE-2026-44476  (opens in a new tab)
CWE-287  (opens in a new tab)
CWE-1390  (opens in a new tab)

How to fix?

Upgrade Chainguard commercial-gitlab-rails-ee-19.3 to version 19.3.3-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream commercial-gitlab-rails-ee-19.3 package and not the commercial-gitlab-rails-ee-19.3 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.