BuildKit has a possible runtime DoS via unbounded group parsing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-61712: 0.40% estimated exploitation activity in the next 30 days; percentile 34.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Maliciously crafted base image or build can cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the buildkitd process. Patches Issue is fixed in BuildKit v0.31.1+ Workarounds Use trusted build sources. References This is BuildKit variant of containerd advisory https://github.com/containerd/containerd/security/advisories/GHSA-jpcc-p29g-p8mq

Published by the source

19 Aug 2026, 20:24 UTC

Last modified by the source

1 Sep 2026, 21:56 UTC

Source last checked

26 Oct 2026, 15:28 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-72x6-4j93-7w86

2. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6256

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-72x6-4j93-7w86

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61712

Advisory: BuildKit has a possible runtime DoS via unbounded group parsing
IDs: CVE-2026-61712, GHSA-72x6-4j93-7w86
Record: https://patchnext.com/advisories/cve-2026-61712 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/moby/buildkit 0.31.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/moby/buildkit: affected <= 0.31.0; fixed in 0.31.1

## Suggested inspection (read-only)
- Go github.com/moby/buildkit: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/moby/buildkit.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-72x6-4j93-7w86 (OSV record GHSA-72x6-4j93-7w86 lists affected ranges: Go github.com/moby/buildkit >=0 <0.31.1 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6256 (OSV record GO-2026-6256 lists affected ranges: Go github.com/moby/buildkit >=0 <0.31.1 (fixed))
- Verified: https://github.com/advisories/GHSA-72x6-4j93-7w86 (GitHub-reviewed advisory GHSA-72x6-4j93-7w86 lists affected ranges: Go github.com/moby/buildkit >=0 <=0.31.0)

Commands are suggestions: review each one before running it.