Is github.com/moby/buildkit 0.30 vulnerable?

Go · 1 release from 0.30.0 to 0.30.0 · latest github.com/moby/buildkit is 0.35.0 · checked 18 Nov 2026

Yes: 4 known advisories

Yes. github.com/moby/buildkit 0.30.0, the last 0.30 release, is affected by 4 known security advisories (1 medium, 3 low), including CVE-2026-61711, CVE-2026-61711, CVE-2026-61712. Upgrade to 0.31.1 or later to fix all of them.

Upgrade with:go get github.com/moby/buildkit@v0.31.1

Is your project on an affected github.com/moby/buildkit?

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/moby/buildkit 0.30.0

  • LowCVE-2026-61711GO-2026-625525 Aug 2026

    BuildKit: Custom frontend could bypass Seccomp/AppArmor in github.com/moby/buildkit

    Affected
    <0.31.1
    Fixed in
    0.31.1
  • LowCVE-2026-61712GO-2026-625625 Aug 2026

    BuildKit has a possible runtime DoS via unbounded group parsing in github.com/moby/buildkit

    Affected
    <0.31.1
    Fixed in
    0.31.1
  • LowCVE-2026-61712GHSA-72x6-4j93-7w8619 Aug 2026

    BuildKit has a possible runtime DoS via unbounded group parsing

    Affected
    <0.31.1
    Fixed in
    0.31.1
  • MediumCVE-2026-61711GHSA-7236-3392-c5c619 Aug 2026

    BuildKit: Custom frontend could bypass Seccomp/AppArmor

    Affected
    <0.31.1
    Fixed in
    0.31.1

Which of your client projects are still on github.com/moby/buildkit 0.30?

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

Other github.com/moby/buildkit 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.