Algorithmic Complexity Affecting gitlab-rails-ce-fips-19.3 package, versions <19.3.1-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.57% (46th 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-GITLABRAILSCEFIPS193-19532687
  • published5 Sept 2026
  • disclosed8 Jul 2026

Introduced: 8 Jul 2026

CVE-2026-59880  (opens in a new tab)
CWE-407  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-rails-ce-fips-19.3 to version 19.3.1-r3 or higher.

NVD Description

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

Immutable.js provides many Persistent Immutable data structures. Prior to 4.3.9 and 5.1.8, Immutable.Map and Immutable.Set keep keys that share the same 32-bit hash in a HashCollisionNode collision bucket that is scanned linearly, allowing an attacker who controls keys inserted into a Map, such as through Immutable.Map(obj), Immutable.fromJS(obj), state.merge(userObject), or mergeDeep, to craft many colliding keys and degrade insertion and lookup to consume disproportionate CPU. This issue is fixed in versions 4.3.9 and 5.1.8.