Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

BuildKit: Custom frontend could bypass Seccomp/AppArmor

CVSS 4.0 5.3 MEDIUMEUVD CVSS 4.0 5.3 CVSS 4.0 · [email protected] · Secondary 5.3 MEDIUMCVSS_V4 Publisher rating MODERATEFixed by github.com/moby/buildkit 0.31.1osv · severity unknownFixed by github.com/moby/buildkit 0.31.1KEV status unknown

cve-program · CVE-2026-61711

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-62838

Published

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.

Read the publisher's advisory

nvd · CVE-2026-61711

Published

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.

Read the publisher's advisory

osv · 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 advisory

osv · GO-2026-6255

Published

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

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-61711

Published

buildkit

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "moby",
                    "product": "buildkit",
                    "versions": [
                        {
                            "version": "< 0.31.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-62838

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 19, 2026, 8:03:38 PM

dateUpdated: Aug 20, 2026, 1:19:05 PM

2 related source bulletins · separate from aliases

WID-SEC-W-2026-2111: docker: Mehrere Schwachstellen

CVE-2026-61711 · CVE-2026-61712 · CVE-2026-61801 · CVE-2026-75593

msrc_CVE-2026-61711: BuildKit: Custom frontend could bypass Seccomp/AppArmor

CVE-2026-61711

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-61711

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-20

Original publisher date fields

published: 2026-08-19T20:17:19.567

lastModified: 2026-09-09T21:15:59.613

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-7236-3392-c5c6

Published

github.com/moby/buildkit

Go

SEMVER · introduced 0 → fixed 0.31.1

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-6255

Published

github.com/moby/buildkit

Go

SEMVER · introduced 0 → fixed 0.31.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 20:56 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current