CVE-2026-61711

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-62838 (ENISA EUVD) · GHSA-7236-3392-c5c6 (GitHub Security Advisories) · GO-2026-6255 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/moby/buildkit @ 0.31.1 (fixes <= 0.31.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 10× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 134 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 34 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-7236-3392-c5c6 · GitHub severity MODERATE
  3. 2026-11-01 07:41 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-30 09:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-25 14:14 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-22 20:00 UTCEG score recompute
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-18 03:25 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 75 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-12 15:50 UTCEG score recompute
  4. 2026-10-11 19:34 UTCEG score recompute
  5. 2026-10-11 16:49 UTCEG score recompute
  6. 2026-10-11 14:11 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-07 10:10 UTCEG score recompute
  13. 2026-10-07 10:10 UTCVendor advisory
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-06 07:55 UTCEG score recompute
  16. 2026-10-06 07:55 UTCVendor advisory
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-04 21:23 UTCVendor advisory
  20. 2026-10-03 16:53 UTCEG score recompute
  21. 2026-10-03 16:53 UTCVendor advisory
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-02 12:56 UTCEG score recompute
  25. 2026-10-02 12:56 UTCVendor advisory
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  27. 2026-10-01 10:43 UTCEG score recompute
  28. 2026-10-01 10:43 UTCVendor advisory
  29. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  30. 2026-09-30 08:37 UTCEG score recompute
  31. 2026-09-30 08:37 UTCVendor advisory
  32. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  33. 2026-09-28 07:57 UTCEG score recompute
  34. 2026-09-28 07:57 UTCVendor advisory
  35. 2026-09-27 05:57 UTCEG score recompute
  36. 2026-09-27 05:57 UTCVendor advisory
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  38. 2026-09-25 03:44 UTCEG score recompute
  39. 2026-09-25 03:44 UTCVendor advisory
  40. 2026-09-24 01:44 UTCEG score recompute
  41. 2026-09-24 01:44 UTCVendor advisory
  42. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-09-22 23:45 UTCEG score recompute
  44. 2026-09-22 23:45 UTCVendor advisory
  45. 2026-09-21 21:11 UTCEG score recompute
  46. 2026-09-21 21:11 UTCVendor advisory
  47. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  48. 2026-09-20 19:11 UTCVendor advisory
  49. 2026-09-19 17:11 UTCEG score recompute
  50. 2026-09-19 17:11 UTCVendor advisory
  51. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  52. 2026-09-18 15:11 UTCEG score recompute
  53. 2026-09-18 15:11 UTCVendor advisory
  54. 2026-09-17 13:11 UTCEG score recompute
  55. 2026-09-17 13:11 UTCVendor advisory
  56. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  57. 2026-09-16 10:46 UTCEG score recompute
  58. 2026-09-16 10:46 UTCVendor advisory
  59. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  60. 2026-09-15 08:36 UTCEG score recompute
  61. 2026-09-15 08:36 UTCVendor advisory
  62. 2026-09-14 06:36 UTCEG score recompute
  63. 2026-09-14 06:36 UTCVendor advisory
  64. 2026-09-13 04:37 UTCEG score recompute
  65. 2026-09-13 04:37 UTCVendor advisory
  66. 2026-09-12 02:37 UTCEG score recompute
  67. 2026-09-12 02:37 UTCVendor advisory
  68. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  69. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  70. 2026-09-11 00:35 UTCEG score recompute
  71. 2026-09-09 03:30 UTCEG score recompute
  72. 2026-09-09 03:30 UTCVendor advisory
  73. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  74. 2026-09-08 01:31 UTCEG score recompute
  75. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61711?
CVE-2026-61711 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-61711 published?
The CVE record for CVE-2026-61711 was published on August 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
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 (29th 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