Back to the CVE list
CVE-2026-121522

Possible panic from Git source resolver

CVSS score

6.7

EPSS probability

—

Risk score

0.7

Published

2 h ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

CVE-2026-121522: Possible BuildKit Interruption from Git Source Resolver

Sources read

1

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

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 [S0]. This interrupts builds handled by that daemon [S0].

Why does it matter?

This vulnerability can cause affected BuildKit daemons to crash and interrupt ongoing build processes, impacting service continuity [S0].

What should be done?

  • Follow official vendor advisories and updates [S0]
  • Consider updating to version v0.34.2 where indicated as fixed [S0]
Chain of evidence and sources2 verified claims

BuildKit v0.26.0 ile v0.34.1 arasındaki sürümlerde, aynı Git kaynak referansı için meta verilerin iki kez çözülmesi daemon'un çökmesine neden olabilir.

Sorun v0.34.2 sürümünde giderilmiştir ancak yama durumu değerlendirmesinde belirsiz olarak sınıflandırılmıştır.

Show the technical text from the sources

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.

CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CWE: CWE-476

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-121522 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1mobybuildkit View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
6.7CVSS V4_0MEDIUMCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVE CNA
6.7CVSS V40MEDIUMCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XNVD

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-121522 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-121522 weaknesses.

Attack Vector and Accessibility

ExposureYerel erişim
PermissionsGerekmiyor
User—

Official Sources and Advisories

CVSS Vector Radar Chart

6.7 / 10
Attack VectorLocalComplexityLowPrivilegesNoneUser Interact.RequiredConfidentialityLowIntegrityNoneAvailabilityHigh

Vulnerability Scoring Details

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Attack VectorLocal
Attack ComplexityLow
Privileges RequiredNone required
User InteractionA
Confidentiality (Gizlilik)Low
Integrity (Bütünlük)A
Availability (Erişilebilirlik)High

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

M
moby logo
moby

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-121522"
CVE-2026-121522 · Possible panic from Git source resolver