CVE-2026-61711

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(low)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 20, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v0.31.1

Patch available: moby/buildkit v0.31.1

https://github.com/moby/buildkit/releases/tag/v0.31.1
github_commit

commit 64bbec89ca43 (moby/buildkit)

Fix landed in moby/buildkit commit 64bbec89ca43 — awaiting tagged release

https://github.com/moby/buildkit/commit/64bbec89ca43dd95b2853edeca240c33c6729910
github_commit

commit 3ea6dd0ce7d2 (moby/buildkit)

Fix landed in moby/buildkit commit 3ea6dd0ce7d2 — awaiting tagged release

https://github.com/moby/buildkit/commit/3ea6dd0ce7d269cdb8aa23348718e2c1bf64f109
github Patch Available

Custom frontend could bypass Seccomp/AppArmor · Advisory · moby/buildkit · GitHub

Affected: versions v0.31.1+

https://github.com/moby/buildkit/security/advisories/GHSA-7236-3392-c5c6

Vendor Advisories for CVE-2026-61711(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/moby/buildkit—0.31.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 14:25 UTCEG score recompute
  3. 2026-08-20 13:33 UTCEG score recompute
  4. 2026-08-19 20:19 UTCEG score recompute
  5. 2026-08-19 20:13 UTCEG score recompute
  6. 2026-08-19 20:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61711?
CVE-2026-61711 is a medium vulnerability published on August 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…
When was CVE-2026-61711 disclosed?
CVE-2026-61711 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61711 actively exploited?
CVE-2026-61711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.0% of all scored CVEs.
What is the CVSS score of CVE-2026-61711?
CVE-2026-61711 has a CVSS v3 base score of 5.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-61711?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61711, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61711

Explore →

Is Your Infrastructure Affected by CVE-2026-61711?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs