Veille CVE

Octobre 2026

10 CVE

Critique 0 Élevée 2 Moyenne 8 Faible 0 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « moby BuildKit » ✕
  1. CVE-2026-93321 6.9 Moyenne

    moby BuildKit

    A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

  2. CVE-2026-93315 5.8 Moyenne

    moby BuildKit

    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 without failing the build.

  3. CVE-2026-93326 6.0 Moyenne

    moby BuildKit

    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 a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.

  4. CVE-2026-93323 6.8 Moyenne

    moby BuildKit

    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 buildkitd allocate memory proportional to that file, potentially exhausting memory and terminating the daemon, which interrupts other builds on the same instance. Fixed by rejecting such files above 16 MiB.

  5. CVE-2026-93322 6.9 Moyenne

    moby BuildKit

    A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

  6. CVE-2026-93320 6.0 Moyenne

    moby BuildKit

    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 unintended host device access.

  7. CVE-2026-93319 5.7 Moyenne

    moby BuildKit

    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.

  8. CVE-2026-93318 7.5 Élevée

    moby BuildKit

    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 cache and snapshot identity without validating that they matched the actual layer contents. If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build using the victim image may mount the attacker-controlled layer contents as the base image. This can allow code from the malicious image to run in the victim build, for example by replacing a commonly executed path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access other build resources, alter output artifacts, or hang the build. The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz.

  9. CVE-2026-93317 5.9 Moyenne

    moby BuildKit

    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 cached under that digest and reused by a later victim build, compromising build-input integrity.

  10. CVE-2026-93316 7.1 Élevée

    moby BuildKit

    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.