Improper Authentication Affecting gitlab-rails-ce-fips-18.11 package, versions <18.11.5-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.24% (16th 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-GITLABRAILSCEFIPS1811-17291421
  • published11 Jun 2026
  • disclosed14 Jul 2026

Introduced: 11 Jun 2026

CVE-2026-45363  (opens in a new tab)
CWE-287  (opens in a new tab)
CWE-326  (opens in a new tab)
CWE-1391  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-rails-ce-fips-18.11 to version 18.11.5-r0 or higher.

NVD Description

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

ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a valid digest under an empty key and no empty-key precondition exists in the HMAC algorithm. The same path is reached when a keyfinder block or key_finder: argument returns an empty string, nil, or an array containing nil for an unknown key, affecting HS256, HS384, and HS512 verification through JWT.decode and JWT::EncodedToken#verify_signature!. This issue is fixed in versions 2.10.3 and 3.2.0.