CSIRTS // UNIFIED SECURITY ADVISORY FEEDSYS ● ONLINE · POWERED BY INTELFUSIONS.COM

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

unknownCVE-2026-61711

CSIRTS triage

What
A custom frontend in BuildKit can bypass Seccomp and AppArmor security policies.
Who is affected
Container deployments using BuildKit with custom frontends and relying on Seccomp or AppArmor confinement.
Urgency
Unknown severity but security policy bypass is critical; treat as urgent pending official guidance.
Action
Apply the BuildKit security fix that prevents custom frontends from bypassing seccomp/apparmor.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch BuildKit

Get an email when a new BuildKit advisory drops — max one per day, one-click unsubscribe.

Details

Source
Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity
unknown
Published
2026-08-11
Exploitation
Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-61711

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Referenced CVEs

CVECSIRTS overviewExternal
CVE-2026-61711coverage & exploitation statusNVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

Recent advisories for BuildKit

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

More from Microsoft Security Response Center