GHSA-2fqp-xg6f-v7gj: Possible panic from Git source resolver

Published Nov 3, 2026
·
Updated

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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade BuildKit to a version that resolves this vulnerability.

    Fixed in v0.34.2

Event History

Nov 3, 2026
CVE Published
via OSV·10:09 PM
Data Sourced
via OSV·10:09 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which BuildKit deployments are affected?

BuildKit versions v0.26.0 through v0.34.1 are affected. The issue is fixed in v0.34.2.

2

What must an attacker provide to trigger the crash?

A build definition must resolve metadata for the same Git source reference twice. Exploitation requires user interaction, as reflected by the UI:A vector.

3

What is the operational impact of successful exploitation?

The BuildKit daemon can panic and crash. Builds being handled by that daemon are interrupted.

4

What should teams do if they are running an affected version?

Upgrade BuildKit to v0.34.2. The provided information does not describe an alternative mitigation for systems that cannot be patched immediately.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203