Is github.com/moby/buildkit 0.31 vulnerable?
Go · 3 releases from 0.31.0 to 0.31.2 · latest github.com/moby/buildkit is 0.35.0 · checked 18 Nov 2026
No known advisories in the last release
github.com/moby/buildkit 0.31.2, the last 0.31 release, has no known advisories. 4 advisories affect earlier 0.31.x releases, so update to 0.31.2.
go get github.com/moby/buildkit@v0.31.2Is your project on an affected github.com/moby/buildkit?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 0.31.x, affecting earlier releases
BuildKit: Custom frontend could bypass Seccomp/AppArmor in github.com/moby/buildkit
- Affected
- <0.31.1
- Fixed in
- 0.31.1
BuildKit has a possible runtime DoS via unbounded group parsing in github.com/moby/buildkit
- Affected
- <0.31.1
- Fixed in
- 0.31.1
BuildKit has a possible runtime DoS via unbounded group parsing
- Affected
- <0.31.1
- Fixed in
- 0.31.1
BuildKit: Custom frontend could bypass Seccomp/AppArmor
- Affected
- <0.31.1
- Fixed in
- 0.31.1
Every github.com/moby/buildkit 0.31.x release
Affected: 0.31.0. 0.31.1 and later are not affected. Latest github.com/moby/buildkit: 0.35.0.
| Version | Known advisories |
|---|---|
| github.com/moby/buildkit 0.31.2 | None |
| github.com/moby/buildkit 0.31.1 | None |
| github.com/moby/buildkit 0.31.0 | CVE-2026-61711, CVE-2026-61712, CVE-2026-61712, CVE-2026-61711 |
Which of your client projects are still on github.com/moby/buildkit 0.31?
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.