Is github.com/containers/buildah 1.42 vulnerable?

Go · 3 releases from 1.42.0 to 1.42.2 · latest github.com/containers/buildah is 1.46.1 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/containers/buildah 1.42.2, the last 1.42 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2026-44517, CVE-2026-44517. At least one has no fixed release yet.

Is your project on an affected github.com/containers/buildah?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/containers/buildah 1.42.2

  • LowCVE-2026-44517GO-2026-511627 Jul 2026

    Build breakout using malicious Containerfile or Git HTTP server in github.com/containers/buildah

    Affected
    >=1.38.1
    Fixed in
    No fix released
  • MediumCVE-2026-44517GHSA-49p4-px3h-rq4922 Jun 2026

    Build breakout using malicious Containerfile and Git Smart HTTP server or GitHub release tar archive

    Affected
    >=1.38.1 <1.43.2
    Fixed in
    1.43.2

Every github.com/containers/buildah 1.42.x release

Affected: 1.42.0 to 1.42.2. Latest github.com/containers/buildah: 1.46.1.

VersionKnown advisories
github.com/containers/buildah 1.42.2CVE-2026-44517, CVE-2026-44517
github.com/containers/buildah 1.42.1CVE-2026-44517, CVE-2026-44517
github.com/containers/buildah 1.42.0CVE-2026-44517, CVE-2026-44517

Which of your client projects are still on github.com/containers/buildah 1.42?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/containers/buildah version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/containers/buildah versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.