Is CVE-2026-44517 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44517 being exploited in the wild.

How severe is CVE-2026-44517?

Medium severity, with a CVSS score of 6.3, published 21 August 2026.

Which products and versions are affected?

Containers Buildah >= 1.38.1, = 1.38.1, < 1.43.2, SEMVER:introduced=1.38.1, SEMVER:introduced=1.38.1,fixed=1.43.2.

Is there a fix for CVE-2026-44517?

Yes. github.com/containers/buildah (Go): upgrade to 1.43.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44517 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-44517?

Check whether you run Containers Buildah or github.com/containers/buildah (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44517: Containers Buildah path traversal in build context processing

Q: Is there a fix for CVE-2026-44517?

Yes. github.com/containers/buildah (Go): upgrade to 1.43.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44517 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-44517?

Check whether you run Containers Buildah or github.com/containers/buildah (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44517 · Severity: medium · CVSS 6.3 · Published 2026-08-21

Buildah is a tool used to create container images. A security flaw allows a malicious server to trick the tool into including sensitive files from the host machine that were not intended to be part of the container. This could lead to the accidental exposure of private data or credentials during the image creation process.

Technologies: github.com/containers/buildah (Go). Vendors: Containers, Go.

Quick answers

Is CVE-2026-44517 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44517 being exploited in the wild.
How severe is CVE-2026-44517?: Medium severity, with a CVSS score of 6.3, published 21 August 2026.
Which products and versions are affected?: Containers Buildah >= 1.38.1, < 1.43.2; github.com/containers/buildah (Go) >= 1.38.1, < 1.43.2, SEMVER:introduced=1.38.1, SEMVER:introduced=1.38.1,fixed=1.43.2.
Is there a fix for CVE-2026-44517?: Yes. github.com/containers/buildah (Go): upgrade to 1.43.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44517 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-44517?: Check whether you run Containers Buildah or github.com/containers/buildah (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/containers/buildah (Go): upgrade to 1.43.2 or later
```
go get github.com/containers/buildah@v1.43.2
```

Technical details

A path traversal vulnerability (CWE-22) exists in Buildah when processing build contexts or 'ADD'/'COPY' instructions. When a user performs a build using a malicious Git Smart HTTP server or a specially crafted GitHub release tar archive, the tool fails to properly restrict file access to the intended build directory. This allows an attacker to cause files from the host's filesystem, located outside the build context, to be included in the resulting container image. The vulnerability is exploited via local execution with user interaction (triggering a build from a malicious source) and has been patched in versions 1.43.2 and 1.44.

Affected products

containers Buildah >= 1.38.1, < 1.43.2

Identifiers

CVE-2026-44517
GHSA-49p4-px3h-rq49
GO-2026-5116

Timeline

2026-06-12: disclosed: Initial disclosure by mheon
2026-06-22: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.