BuildKit: Custom frontend could bypass Seccomp/AppArmor
cve-program · CVE-2026-61711
PublishedBuildKit 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.
Read the publisher's advisoryeuvd · EUVD-2026-62838
PublishedBuildKit 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.
Read the publisher's advisorynvd · CVE-2026-61711
PublishedBuildKit 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.
Read the publisher's advisoryosv · GHSA-7236-3392-c5c6
Published### Impact A custom frontend could send a crafted build request that disabled Seccomp and AppArmor protections for the build container, even if the user did not explicitly allow the `security.insecure` entitlement. Other security measures, like Linux capabilities were still applied to these containers. ### Patches Problem has been fixed in versions v0.31.1+ ### Workarounds Only use BuildKit frontends from trusted providers.
Read the publisher's advisoryosv · GO-2026-6255
PublishedBuildKit: Custom frontend could bypass Seccomp/AppArmor in github.com/moby/buildkit
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-61711 · CVE overview and exploitation status
cve-program · CVE-2026-61711
- https://github.com/moby/buildkit/security/advisories/GHSA-7236-3392-c5c6
- https://github.com/moby/buildkit/commit/3ea6dd0ce7d269cdb8aa23348718e2c1bf64f109
- https://github.com/moby/buildkit/commit/64bbec89ca43dd95b2853edeca240c33c6729910
- https://github.com/moby/buildkit/releases/tag/v0.31.1
euvd · EUVD-2026-62838
- https://github.com/moby/buildkit/security/advisories/GHSA-7236-3392-c5c6
- https://github.com/moby/buildkit/commit/3ea6dd0ce7d269cdb8aa23348718e2c1bf64f109
- https://github.com/moby/buildkit/commit/64bbec89ca43dd95b2853edeca240c33c6729910
- https://github.com/moby/buildkit/releases/tag/v0.31.1
nvd · CVE-2026-61711
- https://github.com/moby/buildkit/commit/3ea6dd0ce7d269cdb8aa23348718e2c1bf64f109
- https://github.com/moby/buildkit/commit/64bbec89ca43dd95b2853edeca240c33c6729910
- https://github.com/moby/buildkit/releases/tag/v0.31.1
- https://github.com/moby/buildkit/security/advisories/GHSA-7236-3392-c5c6
osv · GHSA-7236-3392-c5c6
- https://github.com/moby/buildkit/security/advisories/GHSA-7236-3392-c5c6
- https://github.com/moby/buildkit