Uncontrolled Search Path Element Affecting buildah package, versions <1.44.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.14% (4th 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-BUILDAH-17036465
  • published28 May 2026
  • disclosed5 Jun 2026

Introduced: 28 May 2026

NewCVE-2026-41567  (opens in a new tab)
CWE-427  (opens in a new tab)

How to fix?

Upgrade Chainguard buildah to version 1.44.0-r0 or higher.

NVD Description

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

Moby is an open source container framework. In versions prior to 29.5.1 and in moby/moby v2 prior to v2.0.0-beta.14, when a compressed archive is uploaded to a container via PUT /containers/{id}/archive or piped through docker cp -, the daemon resolves decompression binaries (such as xz or unpigz) from the container's filesystem rather than the host's due to incorrect ordering of operations. A malicious container image containing a trojanized decompression binary can achieve arbitrary code execution with full daemon privileges, including host root UID and unrestricted capabilities, when a user uploads a compressed (xz or gzip) archive into that container. This issue is fixed in Docker Engine 29.5.1 and moby/moby v2.0.0-beta.14. Workarounds include only running containers from trusted images, using authorization plugins to restrict access to the PUT /containers/{id}/archive endpoint, and avoiding piping compressed archives into containers created from untrusted images