37 matches found
SUSE CVE-2026-93319
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...
Linux Distros Unpatched Vulnerability : CVE-2026-93319
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - 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...
Linux Distros Unpatched Vulnerability : CVE-2026-93316
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - 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...
Unsynchronized Access to Shared Data in a Multithreaded Context
Overview Affected versions of this package are vulnerable to Unsynchronized Access to Shared Data in a Multithreaded Context through the container lifecycle handling in frontend/gateway/container/container.go and frontend/gateway/forwarder/forward.go. A malicious external BuildKit frontend can...
Unsynchronized Access to Shared Data in a Multithreaded Context
Overview Affected versions of this package are vulnerable to Unsynchronized Access to Shared Data in a Multithreaded Context through the container lifecycle handling in frontend/gateway/container/container.go and frontend/gateway/forwarder/forward.go. A malicious external BuildKit frontend can...
Unsynchronized Access to Shared Data in a Multithreaded Context
Overview Affected versions of this package are vulnerable to Unsynchronized Access to Shared Data in a Multithreaded Context through the container lifecycle handling in frontend/gateway/container/container.go and frontend/gateway/forwarder/forward.go. A malicious external BuildKit frontend can...
CVE-2026-93316
A flaw was found in BuildKit. This vulnerability allows an authenticated user to cause a Denial of Service DoS by crashing the daemon. When the BuildKit daemon is started with Container Device Interface CDI support disabled, submitting a build that attempts to use CDI devices triggers an unhandle...
CVE-2026-93316
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...
CVE-2026-93319
The BuildKit daemon is vulnerable to a data race condition when a malicious external BuildKit frontend sends requests using the internal API. This vulnerability (classified as CWE-567 ) can lead to a panic of the BuildKit daemon, impacting availability. Remediation information is provided in the ...
CVE-2026-93319 A malicious frontend can cause a daemon panic
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-93319 A malicious frontend can cause a daemon panic
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-93319 A malicious frontend can cause a daemon panic
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...
EUVD-2026-92527
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...
CVE-2026-93316 Starting daemon with --cdi-disabled flag can lead to panic on specific builds
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...
CVE-2026-93316 Starting daemon with --cdi-disabled flag can lead to panic on specific builds
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...
CVE-2026-93316
The BuildKit daemon is vulnerable to a daemon panic when it is started with the --cdi-disabled flag and subsequently processes builds that attempt to use CDI devices . This issue, categorized as a NULL Pointer Dereference (CWE-476) , can occur either accidentally or maliciously. The impact is a h...
PT-2026-106062
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...
PT-2026-106065
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-17113
A flaw was found in CRI-O's container-creation environment-variable handling mergeEnvs in server/utils.go, consumed by setupContainerEnvironmentAndWorkdir in server/containercreate.go. When a CreateContainer request supplies a nil CRI Envs field, CRI-O falls back to using the target OCI image's...
CVE-2026-17113
CRI-O is vulnerable in its container-creation environment-variable handling (mergeEnvs in server/utils.go, consumed by setupContainerEnvironmentAndWorkdir in server/container_create.go). When a CreateContainer request supplies a nil CRI Envs field, CRI-O falls back to the target OCI image's confi...