Answer in brief
CVE-2026-61711 records a Medium severity vulnerability in BuildKit: Custom frontend could bypass Seccomp/AppArmor. The current sources do not mark it as known exploited. The current feed maps moby/buildkit (generic), github.com/moby/buildkit (go), github.com/moby/buildkit (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps moby/buildkit (generic), github.com/moby/buildkit (go), github.com/moby/buildkit (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| moby/buildkitgeneric | < 0.31.1 | Not reported |
| github.com/moby/buildkitgo | >=0 <0.31.1 | 0.31.1 |
| github.com/moby/buildkitgo | <=0.31.0 | 0.31.1 |
Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.