Improper Handling of Length Parameter Inconsistency Affecting gitlab-rails-ce-fips-19.1 package, versions <19.1.2-r7


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.26% (18th 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-GITLABRAILSCEFIPS191-18137435
  • published22 Jul 2026
  • disclosed17 Jul 2026

Introduced: 17 Jul 2026

NewCVE-2026-54466  (opens in a new tab)
CWE-130  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-rails-ce-fips-19.1 to version 19.1.2-r7 or higher.

NVD Description

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

websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.