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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3264 advisory.

    When Trailer headers are sent by a client, the HTTP server internally uses the header values to populate     the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs     memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a Trailer header     that declares a large number of fields causing the server to allocate a disproportionate amount of memory     while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits.This exploit is not applicable     for HTTP/1 servers, which do not support  multiplexing a large number of requests over one TCP connection,     and whose Server.MaxHeaderBytes are calculated differently.Server.MaxHeaderValueCount and     Server.MaxHeaderBytes limits are now applied towards the trailer fields declared in Trailer headers.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81857NOTE: Fixed by:
    https://github.com/golang/go/commit/cbb0fb8b51cba866018b8a0fb4b5458f16c5c80b (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/6e049521882c944afc1e519a83971ec421dc2974 (go1.26.9) (CVE-2026-78659)

    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)

    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. (CVE-2026-93317)

    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. (CVE-2026-93318)

    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)

    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.
    (CVE-2026-93320)

    A malicious frontend can submit an LLB definition that causes buildkitdto panic and terminate,     interrupting all builds running on that daemon. (CVE-2026-93321)

    A malicious frontend can submit an LLB definition that causes buildkitdto panic and terminate,     interrupting all builds running on that daemon. (CVE-2026-93322)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3266 advisory.

    The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the     ApplyLayer helpers) do not confine filesystem operations to the destination directory. A crafted archive     can create or overwrite files outside the intended destination. (CVE-2026-17106)

    When Trailer headers are sent by a client, the HTTP server internally uses the header values to populate     the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs     memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a Trailer header     that declares a large number of fields causing the server to allocate a disproportionate amount of memory     while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits.This exploit is not applicable     for HTTP/1 servers, which do not support  multiplexing a large number of requests over one TCP connection,     and whose Server.MaxHeaderBytes are calculated differently.Server.MaxHeaderValueCount and     Server.MaxHeaderBytes limits are now applied towards the trailer fields declared in Trailer headers.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81857NOTE: Fixed by:
    https://github.com/golang/go/commit/cbb0fb8b51cba866018b8a0fb4b5458f16c5c80b (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/6e049521882c944afc1e519a83971ec421dc2974 (go1.26.9) (CVE-2026-78659)

    When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and     ServeFile(FS) could consume an excessive amount of CPU.

    These functions now ignore Range headers containing more than 200 ranges.The limit is controlled by the     new httpservecontentmaxranges=GODEBUG setting. Setting GODEBUG=httpservecontentmaxranges=0 disables the     limit.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81858NOTE: Fixed by:
    https://github.com/golang/go/commit/ababc3cd873d8acce1777268aa7a817e6b672028 (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/eb25b4e532c5a01f99ef860ec66743a8783f992b (go1.26.9) (CVE-2026-78667)

    The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN     datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent from the host     network namespace of a Linux Swarm node is encrypted with the overlay-network IPsec parameters which meets     the following criteria:

    - UDP datagram- Destination port is the Swarm data-path port- Datagram starts with a VXLAN header for the     VNI of an encrypted overlay network which any running container on the node is connected to     (CVE-2026-92542)

    Docker Engine classifies a registry hostname as insecure using an any-match DNS check.
    loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch     resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR     list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set     of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP     fallback for the registry connection. (CVE-2026-92543)

    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.
    (CVE-2026-93320)

    Parsing a multipart form could bypass memory limits and read an arbitrarily long line into memory when the     remaining limit at the start of a part was less than 400 bytes. Multipart form memory limits are now     properly enforced in this situation.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81741NOTE: Fixed by:
    https://github.com/golang/go/commit/7c79b50a74b6d1aa4269b1827dda7d81f3717f9d (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/d7a7aa8e6781ddf8dce12adf60a813d957d4763e (go1.26.9) (CVE-2026-94440)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of docker installed on the remote host is prior to 25.0.18-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2026-148 advisory.

    The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the     ApplyLayer helpers) do not confine filesystem operations to the destination directory. A crafted archive     can create or overwrite files outside the intended destination. (CVE-2026-17106)

    When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and     ServeFile(FS) could consume an excessive amount of CPU.

    These functions now ignore Range headers containing more than 200 ranges.The limit is controlled by the     new httpservecontentmaxranges=GODEBUG setting. Setting GODEBUG=httpservecontentmaxranges=0 disables the     limit.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81858NOTE: Fixed by:
    https://github.com/golang/go/commit/ababc3cd873d8acce1777268aa7a817e6b672028 (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/eb25b4e532c5a01f99ef860ec66743a8783f992b (go1.26.9) (CVE-2026-78667)

    The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN     datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent from the host     network namespace of a Linux Swarm node is encrypted with the overlay-network IPsec parameters which meets     the following criteria:

    - UDP datagram- Destination port is the Swarm data-path port- Datagram starts with a VXLAN header for the     VNI of an encrypted overlay network which any running container on the node is connected to     (CVE-2026-92542)

    Docker Engine classifies a registry hostname as insecure using an any-match DNS check.
    loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch     resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR     list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set     of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP     fallback for the registry connection. (CVE-2026-92543)

    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.
    (CVE-2026-93320)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of runfinch-finch installed on the remote host is prior to 1.19.0-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2DOCKER-2026-151 advisory.

    When Trailer headers are sent by a client, the HTTP server internally uses the header values to populate     the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs     memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a Trailer header     that declares a large number of fields causing the server to allocate a disproportionate amount of memory     while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits.This exploit is not applicable     for HTTP/1 servers, which do not support  multiplexing a large number of requests over one TCP connection,     and whose Server.MaxHeaderBytes are calculated differently.Server.MaxHeaderValueCount and     Server.MaxHeaderBytes limits are now applied towards the trailer fields declared in Trailer headers.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81857NOTE: Fixed by:
    https://github.com/golang/go/commit/cbb0fb8b51cba866018b8a0fb4b5458f16c5c80b (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/6e049521882c944afc1e519a83971ec421dc2974 (go1.26.9) (CVE-2026-78659)

    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)

    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. (CVE-2026-93317)

    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. (CVE-2026-93318)

    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)

    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.
    (CVE-2026-93320)

    A malicious frontend can submit an LLB definition that causes buildkitdto panic and terminate,     interrupting all builds running on that daemon. (CVE-2026-93321)

    A malicious frontend can submit an LLB definition that causes buildkitdto panic and terminate,     interrupting all builds running on that daemon. (CVE-2026-93322)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of docker installed on the remote host is prior to 25.0.18-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2NITRO-ENCLAVES-2026-124 advisory.

    The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the     ApplyLayer helpers) do not confine filesystem operations to the destination directory. A crafted archive     can create or overwrite files outside the intended destination. (CVE-2026-17106)

    When Trailer headers are sent by a client, the HTTP server internally uses the header values to populate     the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs     memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a Trailer header     that declares a large number of fields causing the server to allocate a disproportionate amount of memory     while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits.This exploit is not applicable     for HTTP/1 servers, which do not support  multiplexing a large number of requests over one TCP connection,     and whose Server.MaxHeaderBytes are calculated differently.Server.MaxHeaderValueCount and     Server.MaxHeaderBytes limits are now applied towards the trailer fields declared in Trailer headers.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81857NOTE: Fixed by:
    https://github.com/golang/go/commit/cbb0fb8b51cba866018b8a0fb4b5458f16c5c80b (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/6e049521882c944afc1e519a83971ec421dc2974 (go1.26.9) (CVE-2026-78659)

    When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and     ServeFile(FS) could consume an excessive amount of CPU.

    These functions now ignore Range headers containing more than 200 ranges.The limit is controlled by the     new httpservecontentmaxranges=GODEBUG setting. Setting GODEBUG=httpservecontentmaxranges=0 disables the     limit.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81858NOTE: Fixed by:
    https://github.com/golang/go/commit/ababc3cd873d8acce1777268aa7a817e6b672028 (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/eb25b4e532c5a01f99ef860ec66743a8783f992b (go1.26.9) (CVE-2026-78667)

    The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN     datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent from the host     network namespace of a Linux Swarm node is encrypted with the overlay-network IPsec parameters which meets     the following criteria:

    - UDP datagram- Destination port is the Swarm data-path port- Datagram starts with a VXLAN header for the     VNI of an encrypted overlay network which any running container on the node is connected to     (CVE-2026-92542)

    Docker Engine classifies a registry hostname as insecure using an any-match DNS check.
    loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch     resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR     list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set     of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP     fallback for the registry connection. (CVE-2026-92543)

    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.
    (CVE-2026-93320)

    Parsing a multipart form could bypass memory limits and read an arbitrarily long line into memory when the     remaining limit at the start of a part was less than 400 bytes. Multipart form memory limits are now     properly enforced in this situation.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81741NOTE: Fixed by:
    https://github.com/golang/go/commit/7c79b50a74b6d1aa4269b1827dda7d81f3717f9d (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/d7a7aa8e6781ddf8dce12adf60a813d957d4763e (go1.26.9) (CVE-2026-94440)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of docker installed on the remote host is prior to 25.0.18-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2DOCKER-2026-152 advisory.

    The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the     ApplyLayer helpers) do not confine filesystem operations to the destination directory. A crafted archive     can create or overwrite files outside the intended destination. (CVE-2026-17106)

    When Trailer headers are sent by a client, the HTTP server internally uses the header values to populate     the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs     memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a Trailer header     that declares a large number of fields causing the server to allocate a disproportionate amount of memory     while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits.This exploit is not applicable     for HTTP/1 servers, which do not support  multiplexing a large number of requests over one TCP connection,     and whose Server.MaxHeaderBytes are calculated differently.Server.MaxHeaderValueCount and     Server.MaxHeaderBytes limits are now applied towards the trailer fields declared in Trailer headers.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81857NOTE: Fixed by:
    https://github.com/golang/go/commit/cbb0fb8b51cba866018b8a0fb4b5458f16c5c80b (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/6e049521882c944afc1e519a83971ec421dc2974 (go1.26.9) (CVE-2026-78659)

    When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and     ServeFile(FS) could consume an excessive amount of CPU.

    These functions now ignore Range headers containing more than 200 ranges.The limit is controlled by the     new httpservecontentmaxranges=GODEBUG setting. Setting GODEBUG=httpservecontentmaxranges=0 disables the     limit.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81858NOTE: Fixed by:
    https://github.com/golang/go/commit/ababc3cd873d8acce1777268aa7a817e6b672028 (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/eb25b4e532c5a01f99ef860ec66743a8783f992b (go1.26.9) (CVE-2026-78667)

    The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN     datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent from the host     network namespace of a Linux Swarm node is encrypted with the overlay-network IPsec parameters which meets     the following criteria:

    - UDP datagram- Destination port is the Swarm data-path port- Datagram starts with a VXLAN header for the     VNI of an encrypted overlay network which any running container on the node is connected to     (CVE-2026-92542)

    Docker Engine classifies a registry hostname as insecure using an any-match DNS check.
    loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch     resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR     list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set     of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP     fallback for the registry connection. (CVE-2026-92543)

    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.
    (CVE-2026-93320)

    Parsing a multipart form could bypass memory limits and read an arbitrarily long line into memory when the     remaining limit at the start of a part was less than 400 bytes. Multipart form memory limits are now     properly enforced in this situation.

    NOTE: https://www.openwall.com/lists/oss-security/2026/10/08/9NOTE:
    https://github.com/golang/go/issues/81741NOTE: Fixed by:
    https://github.com/golang/go/commit/7c79b50a74b6d1aa4269b1827dda7d81f3717f9d (go1.27.2)NOTE: Fixed by:
    https://github.com/golang/go/commit/d7a7aa8e6781ddf8dce12adf60a813d957d4763e (go1.26.9) (CVE-2026-94440)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2026-93320)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
371901	Amazon Linux 2023 : runfinch-finch (ALAS2023-2026-3264)	Nessus	Amazon Linux Local Security Checks	Local	high
371886	Amazon Linux 2023 : docker (ALAS2023-2026-3266)	Nessus	Amazon Linux Local Security Checks	Local	high
371825	Amazon Linux 2 : docker (ALASECS-2026-148)	Nessus	Amazon Linux Local Security Checks	Local	high
371810	Amazon Linux 2 : runfinch-finch (ALASDOCKER-2026-151)	Nessus	Amazon Linux Local Security Checks	Local	high
371780	Amazon Linux 2 : docker (ALASNITRO-ENCLAVES-2026-124)	Nessus	Amazon Linux Local Security Checks	Local	high
371764	Amazon Linux 2 : docker (ALASDOCKER-2026-152)	Nessus	Amazon Linux Local Security Checks	Local	high
363331	Linux Distros Unpatched Vulnerability : CVE-2026-93320	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-93320

medium

Tenable Plugins

high

high

high

high

high

high

medium