CVE-2026-61711 BuildKit: Custom frontend could bypass Seccomp/AppArmor
A custom frontend can bypass Seccomp and AppArmor protections in BuildKit by submitting an invalid security mode, weakening container isolation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-61711?
CVE-2026-61711 is a medium-severity vulnerability in moby buildkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to 0.31.1, a custom frontend could place an invalid SecurityMode value in a crafted build request, and executor/oci/spec_linux.go treated the unsupported value as a non-sandbox mode without requiring the security.insecure entitlement. This disabled Seccomp and AppArmor protections for the build container even though Linux capabilities remained restricted. This issue is fixed in version 0.31.1.
Weakness: CWE-20
Which versions are affected by CVE-2026-61711?
3 open source packages ship an affected version, including github.com/moby/buildkit.
| Package | Affected | Fixed in |
|---|---|---|
github.com/moby/buildkit Go | All versions | 0.31.1 |
github.com/moby/buildkit Go | All versions | 0.31.1 |
github.com/moby/buildkit Go | All versions | 0.31.1 |
How do I fix CVE-2026-61711?
Upgrade github.com/moby/buildkit to 0.31.1 or later.
Is CVE-2026-61711 being exploited?
There is no known exploitation of CVE-2026-61711 in the wild and no public exploit code.
Sources
Also known as AZL-97032, ECHO-7696-5a12-0f6d, GHSA-7236-3392-c5c6, GO-2026-6255, MINI-2g6v-cvg4-98cx, MINI-2v6m-f974-fqvf and 41 more.