DeutschShown in its original language — a full translation is planned for a future version.
BuildKit: Mehrere Schwachstellen
view advisory published 2026-10-05
Ein Angreifer kann mehrere Schwachstellen in BuildKit ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen sowie einen Denial-of-Service-Zustand auszulösen.
01
describes (10)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-93321US | — | — | ||
A malicious frontend can submit an LLB definition that causes buildkitd
to panic and terminate, interrupting all builds running on that daemon. | ||||
| CVE-2026-93315US | — | — | ||
When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup. This may cause cleanup to block, operate outside the build rootfs, or fail with… | ||||
| CVE-2026-93326US | — | — | ||
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from… | ||||
| CVE-2026-93323US | — | — | ||
The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit. A build context containing an oversized file could make b… | ||||
| CVE-2026-93322US | — | — | ||
A malicious frontend can submit an LLB definition that causes buildkitd
to panic and terminate, interrupting all builds running on that daemon. | ||||
| CVE-2026-93320US | — | — | ||
BuildKit may be tricked into performing file actions with special file inodes where regular files are expected. Special files may block operations or, on rootful workers, allow uni… | ||||
| CVE-2026-93319US | — | — | ||
A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic. | ||||
| CVE-2026-93318US | — | — | ||
A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cach… | ||||
| CVE-2026-93317US | — | — | ||
An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cach… | ||||
| CVE-2026-93316US | — | — | ||
If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident. | ||||
02
references
External citations — patches, advisories, analysis.
- Amazon Linux Security Advisory ALAS2DOCKER-2026-151 vom 2026-10-25external
- Amazon Linux Security Advisory ALAS2DOCKER-2026-152 vom 2026-10-25external
- Amazon Linux Security Advisory ALAS2ECS-2026-148 vom 2026-10-25external
- Amazon Linux Security Advisory ALAS2NITRO-ENCLAVES-2026-124 vom 2026-10-25external
- GitHub Security Database vom 2026-10-05external
- GitHub Security Database vom 2026-10-05external
- GitHub Security Database vom 2026-10-05external
- GitHub Security Database vom 2026-10-05external
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan