Resource Exhaustion The advisory has been revoked - it doesn't affect any version of package gitlab-rails-ce-fips-18.1 (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-GITLABRAILSCEFIPS181-14912825
- published12 Jan 2026
- disclosed7 Oct 2025
Introduced: 7 Oct 2025
CVE-2025-61771 (opens in a new tab)Amendment
The Chainguard security team deemed this advisory irrelevant for Chainguard:latest.
NVD Description
Note: Versions mentioned in the description apply only to the upstream gitlab-rails-ce-fips-18.1 package and not the gitlab-rails-ce-fips-18.1 package as distributed by Chainguard.
Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, ``Rack::Multipart::Parserstores non-file form fields (parts without afilename) entirely in memory as Ruby Stringobjects. A single large text field in a multipart/form-data request (hundreds of megabytes or more) can consume equivalent process memory, potentially leading to out-of-memory (OOM) conditions and denial of service (DoS). Attackers can send large non-file fields to trigger excessive memory usage. Impact scales with request size and concurrency, potentially leading to worker crashes or severe garbage-collection overhead. All Rack applications processing multipart form submissions are affected. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a reasonable size cap for non-file fields (e.g., 2 MiB). Workarounds include restricting maximum request body size at the web-server or proxy layer (e.g., Nginxclient_max_body_size`) and validating and rejecting unusually large form fields at the application level.