← Search results
CVE-LINKED INVENTORY25 SECURITY RECORDS
moby
BuildKit
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at buildkit, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-93321 | 5 Oct 2026 | BuildKit: ≤ 0.33.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93315 | 5 Oct 2026 | BuildKit: 0.31.0 < 0.33.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93326 | 5 Oct 2026 | BuildKit: ≤ 0.33.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93323 | 5 Oct 2026 | BuildKit: ≤ 0.33.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93322 | 5 Oct 2026 | BuildKit: ≤ 0.33.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93320 | 5 Oct 2026 | BuildKit: ≤ 0.33.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93319 | 5 Oct 2026 | BuildKit: ≤ 0.33.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93318 | 5 Oct 2026 | BuildKit: < 0.33.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93317 | 5 Oct 2026 | BuildKit: 0.28.0 < 0.33.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-93316 | 5 Oct 2026 | BuildKit: < 0.33.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-75593 | 19 Aug 2026 | < 0.31.2 | 0.31.2. | Update reference ↗ |
| CVE-2026-61711 | 19 Aug 2026 | < 0.31.1 | 0.31.1. | Update reference ↗ |
| CVE-2026-61712 | 19 Aug 2026 | < 0.31.1 | 0.31.1. | Update reference ↗ |
| CVE-2026-15793 | 21 Jul 2026 | 0.30.0 ≤ 0.31.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-15792 | 21 Jul 2026 | < 0.31.2 | For OpenShift Container Platform 4.18 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/release_notes/ocp-4-18-release-notes For Red Hat OpenShift Logging 6.2, see the following instructions to apply this update: https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.2 | Update reference ↗ |
| CVE-2026-15791 | 21 Jul 2026 | 0.10.0 < 0.31.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-15789 | 21 Jul 2026 | < 0.31.2 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-15788 | 20 Jul 2026 | < 0.31.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33748 | 27 Mar 2026 | < 0.28.1 | Before applying this update, make sure all previously released errata relevant to your system have been applied. | Update reference ↗ |
| CVE-2026-33747 | 27 Mar 2026 | < 0.28.1 | Before applying this update, make sure all previously released errata relevant to your system have been applied. | Update reference ↗ |
| CVE-2024-23653 | 31 Jan 2024 | < 0.12.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-23652 | 31 Jan 2024 | < 0.12.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-23651 | 31 Jan 2024 | < 0.12.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-23650 | 31 Jan 2024 | < 0.12.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-26054 | 6 Mar 2023 | >= 0.10.0, < 0.11.4 | For OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags The sha values for the release are: (For x86_64 architecture) The image digest is sha256:bc9835804046aa844c874d2cc37387ec95fe7e87d8ce96129fba78d465c932fa (For s390x architecture) The image digest is sha256:c26d48b04d8864fc20145204b543957824d1d86696c82efdd9738d096796326d (For ppc64le architecture) The image digest is sha256:2bf60fe7b0c72a301aa26544e3faabb61fe750e449ee130ee6945b588a727e67 (For aarch64 architecture) The image digest is sha256:f61d496a3b69582f0f1c54da973a58241b3e6001d8d1a696368d604b9ae774f2 All OpenShift Container Platform 4.13 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift Console or the CLI oc command. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.13/updating/updating-cluster-cli.html | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.