Homepage

Uncontrolled Memory Allocation Affecting gitlab-operator-fips package, versions <3.2.0-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.72% (52nd 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-GITLABOPERATORFIPS-18007732
  • published17 Jul 2026
  • disclosed14 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 17 Jul 2026

CVE-2026-53716  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-operator-fips to version 3.2.0-r0 or higher.

NVD Description

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

Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, getFileFromGZ in internal/wasm/httpfetcher.go calls io.ReadAll on a gzip.Reader without limiting decompressed output when a tenant-controlled EnvoyExtensionPolicy.spec.wasm[].code.http.url points to a reachable compressed Wasm payload. The 256 MiB compressed-input cap does not constrain the expanded size, no operator Wasm URL allowlist exists, and the optional sha256 check occurs only after decompression, so a comparatively small gzip stream can force a multi-gigabyte allocation in the shared controller. The resulting out-of-memory termination restarts the controller, re-reconciles the persistent custom resource, and can create a persistent cross-tenant control-plane outage. This issue is fixed in versions 1.7.4 and 1.8.1.