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

    Arithmetic over induction variables in loops were not correctly checked for underflow or overflow in the     Go compiler (cmd/compile). As a result, the compiler would allow for invalid indexing to occur at runtime,     potentially leading to memory corruption in programs compiled with affected Go versions. (CVE-2026-27143)

    The Go compiler (cmd/compile) incorrectly handled no-op interface conversions, preventing correct     determination about non-overlapping memory moves, potentially leading to memory corruption at runtime in     programs compiled with affected Go versions. (CVE-2026-27144)

    During chain building, the amount of work that is done is not correctly limited when a large number of     intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of     service. This affects both direct users of crypto/x509 and users of crypto/tls. (CVE-2026-32280)

    Validating certificate chains which use policies is unexpectedly inefficient when certificates in the     chain contain a very large number of policy mappings, possibly causing denial of service. This only     affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots     CertPool, or in the system certificate pool. (CVE-2026-32281)

    On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress,     Chmod can operate on the target of the symlink, even when the target lies outside the root.
    (CVE-2026-32282)

    If one side of the TLS connection sends multiple key update messages post-handshake in a single record,     the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of     service. This only affects TLS 1.3. (CVE-2026-32283)

    tar.Reader can allocate an unbounded amount of memory when reading a maliciously-crafted archive     containing a large number of sparse regions encoded in the old GNU sparse map format. (CVE-2026-32288)

    Context was not properly tracked across template branches for JS template literals, leading to possibly     incorrect escaping of content. This could cause actions within JS template literals to be incorrectly     escaped, leading to XSS vulnerabilities. (CVE-2026-32289)

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg     field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW,     and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in     key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the     encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() /     ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take     a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping     algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by     calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling     this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed     in 4.1.4 and 3.0.5. (CVE-2026-34986)

    OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters     (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap.
    This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled     (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.
    (CVE-2026-39882)

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.

Detections

Analytics

Amazon Linux 2023 : containerd, containerd-stress (ALAS2023-2026-1606)

critical Nessus Plugin ID 311317

Version 1.2

Version 1.1

Version 1.2 May 12, 2026, 8:32 AM CVE (set "CVE" coverage to "CVE-2026-27143,CVE-2026-27144,CVE-2026-32280,CVE-2026-32281,CVE-2026-32282,CVE-2026-32283,CVE-2026-32288,CVE-2026-32289,CVE-2026-34986,CVE-2026-39882") Plugin metadata Plugin Feed: 202605120832
Version 1.1 May 1, 2026, 7:22 AM New Plugin Feed: 202605010722