CVE-2026-61711

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (27th percentile of EPSS-scored CVEs). 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: epss, 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.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 9, 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(2)

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 rangeFix by version rangeDependents
github.com/moby/buildkit—
  • every version up to 0.31.1: fixed in 0.31.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 61× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 21:23 UTCVendor advisory
  3. 2026-10-03 16:53 UTCEG score recompute
  4. 2026-10-03 16:53 UTCVendor advisory
  5. 2026-10-03 14:26 UTCEPSS rescore
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 12:56 UTCEG score recompute
  8. 2026-10-02 12:56 UTCVendor advisory
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-10-01 10:43 UTCEG score recompute
  11. 2026-10-01 10:43 UTCVendor advisory
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-30 08:37 UTCEG score recompute
  14. 2026-09-30 08:37 UTCVendor advisory
  15. 2026-09-28 13:51 UTCEPSS rescore
  16. 2026-09-28 07:57 UTCEG score recompute
  17. 2026-09-28 07:57 UTCVendor advisory
  18. 2026-09-27 05:57 UTCEG score recompute
  19. 2026-09-27 05:57 UTCVendor advisory
  20. 2026-09-26 15:59 UTCEPSS rescore
  21. 2026-09-25 03:44 UTCEG score recompute
  22. 2026-09-25 03:44 UTCVendor advisory
  23. 2026-09-24 01:44 UTCEG score recompute
  24. 2026-09-24 01:44 UTCVendor advisory
  25. 2026-09-23 17:54 UTCEPSS rescore
Show 67 more
  1. 2026-09-22 23:45 UTCEG score recompute
  2. 2026-09-22 23:45 UTCVendor advisory
  3. 2026-09-21 21:11 UTCEG score recompute
  4. 2026-09-21 21:11 UTCVendor advisory
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-20 19:11 UTCVendor advisory
  7. 2026-09-19 17:11 UTCEG score recompute
  8. 2026-09-19 17:11 UTCVendor advisory
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 15:11 UTCEG score recompute
  11. 2026-09-18 15:11 UTCVendor advisory
  12. 2026-09-17 13:11 UTCEG score recompute
  13. 2026-09-17 13:11 UTCVendor advisory
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 10:46 UTCEG score recompute
  16. 2026-09-16 10:46 UTCVendor advisory
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 08:36 UTCEG score recompute
  19. 2026-09-15 08:36 UTCVendor advisory
  20. 2026-09-14 06:36 UTCEG score recompute
  21. 2026-09-14 06:36 UTCVendor advisory
  22. 2026-09-13 04:37 UTCEG score recompute
  23. 2026-09-13 04:37 UTCVendor advisory
  24. 2026-09-12 02:37 UTCEG score recompute
  25. 2026-09-12 02:37 UTCVendor advisory
  26. 2026-09-11 14:53 UTCEPSS rescore
  27. 2026-09-11 09:37 UTCEPSS rescore
  28. 2026-09-11 00:35 UTCEG score recompute
  29. 2026-09-09 03:30 UTCEG score recompute
  30. 2026-09-09 03:30 UTCVendor advisory
  31. 2026-09-08 22:01 UTCEPSS rescore
  32. 2026-09-08 01:31 UTCEG score recompute
  33. 2026-09-07 16:01 UTCEPSS rescore
  34. 2026-09-06 23:30 UTCEG score recompute
  35. 2026-09-06 13:47 UTCEPSS rescore
  36. 2026-09-05 21:30 UTCEG score recompute
  37. 2026-09-04 19:31 UTCEG score recompute
  38. 2026-09-04 05:07 UTCEPSS rescore
  39. 2026-09-02 15:15 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescore
  41. 2026-09-01 13:54 UTCEPSS rescore
  42. 2026-09-01 12:55 UTCEG score recompute
  43. 2026-09-01 04:40 UTCEPSS rescore
  44. 2026-08-31 10:34 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescore
  46. 2026-08-30 08:31 UTCEG score recompute
  47. 2026-08-30 01:22 UTCEPSS rescore
  48. 2026-08-29 06:31 UTCEG score recompute
  49. 2026-08-28 21:42 UTCEPSS rescore
  50. 2026-08-28 04:29 UTCEG score recompute
  51. 2026-08-27 14:25 UTCEPSS rescore
  52. 2026-08-27 02:29 UTCEG score recompute
  53. 2026-08-26 14:46 UTCEPSS rescore
  54. 2026-08-26 00:29 UTCEG score recompute
  55. 2026-08-25 13:49 UTCEPSS rescore
  56. 2026-08-24 22:29 UTCEG score recompute
  57. 2026-08-23 20:29 UTCEG score recompute
  58. 2026-08-23 00:19 UTCEPSS rescore
  59. 2026-08-22 18:29 UTCEG score recompute
  60. 2026-08-21 23:49 UTCEPSS rescore
  61. 2026-08-21 16:28 UTCEG score recompute
  62. 2026-08-20 22:55 UTCEPSS rescore
  63. 2026-08-20 14:25 UTCEG score recompute
  64. 2026-08-20 13:33 UTCEG score recompute
  65. 2026-08-19 20:19 UTCEG score recompute
  66. 2026-08-19 20:13 UTCEG score recompute
  67. 2026-08-19 20:12 UTCMITRE cvelistV5first tracked

Related CVEs(same product + 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 on August 19, 2026, with the most recent update on September 9, 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.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61711?
CVE-2026-61711 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61711?
A fix for CVE-2026-61711 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61711 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs