CVE-2026-61711Network attack vector

Seccomp AppArmor bypass via invalid SecurityMode

Published Aug 19, 2026 · Updated Aug 20, 2026

Security-feature bypass in Moby BuildKit before 0.31.1 allows remote authenticated users to disable Seccomp and AppArmor via crafted build requests. In executor/oci/spec_linux.go, unsupported SecurityMode enum values were treated as non-sandbox execution, and client/llb/exec.go did not reject invalid values before marshalling executor specs until the fix added explicit validation. Exploitation requires the ability to supply a custom frontend or low-level build request; Linux capabilities remained restricted, so the issue weakens container isolation rather than establishing a demonstrated host escape.

CVSS severity6.3
Medium
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Security-feature bypass in Moby BuildKit before 0.31.1 allows remote authenticated users to disable Seccomp and AppArmor via crafted build requests. In executor/oci/spec_linux.go, unsupported SecurityMode enum values were treated as non-sandbox execution, and client/llb/exec.go did not reject invalid values before marshalling executor specs until the fix added explicit validation. Exploitation requires the ability to supply a custom frontend or low-level build request; Linux capabilities remained restricted, so the issue weakens container isolation rather than establishing a demonstrated host escape.

The record

CVE
CVE-2026-61711
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
Moby Project
Product
BuildKit
Classifications
CWE-20, T1562
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.31.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Moby Project · BuildKitversion=< 0.31.1

Published CVSS scores

6.3GitLab Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-20Improper Input Validation
T1562Impair Defenses

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo