In BuildKit versions v0.26.0 through v0.34.1, a specific build definition that resolves metadata for the same Git source reference twice can cause the BuildKit daemon to panic and crash, interrupting builds handled by that daemon. The issue is fixed in v0.34.2.
CVE-2026-121522
MEDIUMPre-NVD 6.76.7Trending — Patch released this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st 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
Also known asEUVD-2026-116537 (ENISA EUVD)Source: ENISA EUVD
6.7EG
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.1%CVSS: 6.7Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
Fixed versions, as the CVE record's CNA (Docker Inc.) states them: "Upgrade BuildKit to v0.34.2 or later."
- CVSS v3
- 6.7
- EG Score
- 6.7MEDIUMmedium confidence
- EG Risk
- 30EG Risk 30/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)Severity67% × 45%Impact severity (EG Severity): CVSS 6.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 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.1%
- EPSS %ILE
- 1st
- 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 (6.7): severity, escalated by confirmed exploitation. This CVE's 6.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.7 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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). 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
November 3, 2026
Last Modified
November 6, 2026
Advisory Details (1)
Auto-updated Nov 6, 2026Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)
Possible panic from Git source resolver · Advisory · moby/buildkit · GitHub
https://github.com/moby/buildkit/security/advisories/GHSA-2fqp-xg6f-v7gjVendor Advisories for CVE-2026-121522(1)
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 / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | podman-main-6.1.4-1.3.hum1 | 2026-11-05 | redhat |
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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.
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-06 21:48 UTCVendor advisory
- 2026-11-06 20:28 UTCEG score recompute
- 2026-11-06 20:28 UTCVendor advisory
- 2026-11-06 19:37 UTCEG score recompute
- 2026-11-06 19:37 UTCVendor advisory
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-03 23:03 UTCENISA EUVD ID recordedEUVD-2026-116537 · Source: ENISA EUVD
- 2026-11-03 22:33 UTCEG score recompute
- 2026-11-03 22:16 UTCEG score recomputeFirst assessed: 6.7 MEDIUM
- 2026-11-03 22:16 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Frequently asked(5)
What is CVE-2026-121522?
CVE-2026-121522 is a medium-severity vulnerability; its CVE record was published on November 3, 2026. In BuildKit versions v0.26.0 through v0.34.1, a specific build definition that resolves metadata for the same Git source reference twice can cause the BuildKit daemon to panic and crash, interrupting builds handled by that daemon. The issue is fixed in v0.34.2.
When was the CVE record for CVE-2026-121522 published?
The CVE record for CVE-2026-121522 was published on November 3, 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-121522 actively exploited?
CVE-2026-121522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-121522?
CVE-2026-121522 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-121522?
A fix for CVE-2026-121522 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Docker Inc.) states them: "Upgrade BuildKit to v0.34.2 or later." The vendor advisories EchelonGraph has for CVE-2026-121522 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-121522
Is Your Infrastructure Affected by CVE-2026-121522?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.