CVE-2026-90711 Affecting commercial-gitlab-rails-ee-19.4 package, versions <19.4.1-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.33% (24th 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-COMMERCIALGITLABRAILSEE194-20651851
  • published8 Oct 2026
  • disclosed15 Sept 2026

Introduced: 15 Sep 2026

CVE-2026-90711  (opens in a new tab)

How to fix?

Upgrade Chainguard commercial-gitlab-rails-ee-19.4 to version 19.4.1-r1 or higher.

NVD Description

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

proxy-addr is a Node.js module that determines a request's client address behind trusted reverse proxies, and it backs Express req.ip and req.ips. In versions 1.1.0 through 2.0.7, a trust subnet written in IPv4-mapped IPv6 notation with an IPv4-sized prefix, such as ::ffff:10.0.0.0/8 instead of the correct ::ffff:10.0.0.0/104, is accepted without error but trusts every IPv4 address on the internet rather than the block it names. Because the socket peer then becomes trusted at hop 0, any unauthenticated client can supply an arbitrary X-Forwarded-For header and control the address the application reads, which defeats IP-based access control, rate limiting, geolocation, and audit logging. This is a fail-open regression introduced in version 1.1.0. The issue is fixed in proxy-addr 2.0.8, and users should upgrade to 2.0.8 or later. As a workaround, ensure any IPv4-mapped IPv6 trust subnet uses a prefix length of at least 97, or express the range in plain IPv4 notation.

CVSS Base Scores

version 3.1