Homepage

Uncontrolled Memory Allocation Affecting datadog-cluster-agent-fips-7 package, versions <7.81.1-r1

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-MINIMOSLATEST-DATADOGCLUSTERAGENTFIPS7-18015944
  • published19 Jul 2026
  • disclosed14 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 19 Jul 2026

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

How to fix?

Upgrade Minimos:latest datadog-cluster-agent-fips-7 to version 7.81.1-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream datadog-cluster-agent-fips-7 package and not the datadog-cluster-agent-fips-7 package as distributed by Minimos. See How to fix? for Minimos:latest 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, internal/wasm/imagefetcher.go follows tenant-controlled EnvoyExtensionPolicy spec.wasm[].code.image.url values to Docker or OCI Wasm layers, and extractWasmPluginBinary uses the untrusted tar-header h.Size value to allocate memory before validating the entry name or declared size. A small PAX or GNU tar header can therefore claim a multi-terabyte entry even though the surrounding LimitReader restricts only the bytes read from the stream, and no registry allowlist prevents a permitted tenant from selecting an attacker-controlled registry that the controller can reach. The allocation is attempted for every tar entry and can cause an unrecoverable Go runtime out-of-memory failure; because the custom resource persists, reconciliation repeatedly crash-loops the shared controller and causes a single-request, non-volumetric, cluster-wide control-plane denial of service. This issue is fixed in versions 1.7.4 and 1.8.1.