Buildah lacks limits on repository paths when fetching source code or archives. A malicious server that delivers a Git repository or a tarball can embed symbolic links that point outside the intended build context. When Buildah copies the content into the build, the missing confinement allows files from outside the context to be read or written, potentially exposing credentials, configuration files, or enabling code execution in the build environment, as reflected by CWE‑22.

The vulnerability affects Buildah containers:buildah versions 1.38.1 through 1.43.2 and the 1.44.0 release. The issue is resolved in 1.43.2 and 1.44.0. Earlier or later versions are not affected.

The CVSS score of 6.3 indicates a moderate severity and the EPSS score is not available, suggesting no known exploitation data. However, because the flaw can be triggered by any untrusted source accessed over the network (e.g., a public Git service or an HTTP mirror) and can alter the build context, an attacker can potentially introduce malicious files into the image during normal operation. The risk is therefore significant for environments that pull from untrusted sources, while the likelihood of exploitation depends on user practices rather than a public exploit.