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

    Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC)     identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to     bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can     trigger GET requests, the request cannot mutate state. The response from the GET request is not returned     to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal     network through Blind SSRF. This vulnerability is fixed in 1.8.5. (CVE-2026-22772)

    sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3     and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs     a filesystem path by joining a cache base directory with a target name sourced from signed target     metadata; however, it does not validate that the resulting path stays within the cache base directory. A     malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the     calling process has. Note that this should only affect clients that are directly using the TUF client in     sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are     unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed     in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting     SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-     go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release. (CVE-2026-24137)

    go-tuf is a Go implementation of The Update Framework (TUF). go-tuf's TAP 4 Multirepo Client uses the map     file repository name string (`repoName`) as a filesystem path component when selecting the local metadata     cache directory. Starting in version 2.0.0 and prior to version 2.4.1, if an application accepts a map     file from an untrusted source, an attacker can supply a `repoName` containing traversal (e.g.,     `../escaped-repo`) and cause go-tuf to create directories and write the root metadata file outside the     intended `LocalMetadataDir` cache base, within the running process's filesystem permissions. Version 2.4.1     contains a patch. (CVE-2026-24686)

    url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
    (CVE-2026-25679)

    On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the     returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of     this escape is limited to reading metadata provided by lstat from arbitrary locations on the filesystem     without permitting reading or writing files outside the root. (CVE-2026-27139)

    Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS     if the meta tag also has an http-equiv attribute with the value refresh. A new GODEBUG setting has been     added, htmlmetacontenturlescape, which can be used to disable escaping URLs in actions in the meta content     attribute which follow url= by setting htmlmetacontenturlescape=0. (CVE-2026-27142)

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 soci-snapshotter installed on the remote host is prior to 0.13.0-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2DOCKER-2026-107 advisory.

    url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
    (CVE-2026-25679)

    On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the     returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of     this escape is limited to reading metadata provided by lstat from arbitrary locations on the filesystem     without permitting reading or writing files outside the root. (CVE-2026-27139)

    Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS     if the meta tag also has an http-equiv attribute with the value refresh. A new GODEBUG setting has been     added, htmlmetacontenturlescape, which can be used to disable escaping URLs in actions in the meta content     attribute which follow url= by setting htmlmetacontenturlescape=0. (CVE-2026-27142)

    gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass     resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too     lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash     (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests     to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated     the raw, non-canonical path string. Consequently, deny rules defined using canonical paths (starting     with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback allow     rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the     official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on     `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific deny rules     for canonical paths but allows other requests by default (a fallback allow rule). The vulnerability is     exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the     gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a     leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching     authorization interceptors or handlers with a non-canonical path string. While upgrading is the most     secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use     a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy     hardening. (CVE-2026-33186)

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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0947-1 advisory.

    Update to go 1.25.8 (bsc#1244485, jsc#SLE-18320):

    - CVE-2025-61732: cmd/cgo: discrepancy between Go and C/C++ comment parsing allows for C code smuggling     (bsc#1257692).
    - CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session     resumption does       not account for the expiration of full certificate chain (bsc#1256818).
    - CVE-2026-25679: net/url: reject IPv6 literal not at start of host (bsc#1259264).
    - CVE-2026-27139: os: FileInfo can escape from a Root (bsc#1259268).
    - CVE-2026-27142: html/template: URLs in meta content attribute actions are not escaped (bsc#1259265).

    Changelog:

     * go#77253 cmd/compile: miscompile of global array initialization
     * go#77406 os: Go 1.25.x regression on RemoveAll for windows
     * go#77413 runtime: netpollinit() incorrectly prints the error from linux.Eventfd
     * go#77438 cmd/go: CGO compilation fails after upgrading from Go 1.25.5 to 1.25.6 due to --define-     variable flag in        pkg-config
     * go#77531 net/smtp: expiry date of localhostCert for testing is too short
     * go#75844 cmd/compile: OOM killed on linux/arm64
     * go#77323 crypto/x509: single-label excluded DNS name constraints incorrectly match all wildcard SANs
     * go#77425 crypto/tls: CL 737700 broke session resumption on macOS

Tenable has extracted the preceding description block directly from the SUSE 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 cni-plugins installed on the remote host is prior to 1.7.1-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-3311 advisory.

    Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS     if the meta tag also has an http-equiv attribute with the value refresh. A new GODEBUG setting has been     added, htmlmetacontenturlescape, which can be used to disable escaping URLs in actions in the meta content     attribute which follow url= by setting htmlmetacontenturlescape=0. (CVE-2026-27142)

    When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of     C memory and a crash. (CVE-2026-33811)

    When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION     frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0. (CVE-2026-33814)

    Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive     CPU exhaustion and memory allocations. (CVE-2026-39820)

    CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's     <content> attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the     <content> attribute, the escaper would fail to similarly escape it, leading to XSS. (CVE-2026-39823)

    Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC     5322. (CVE-2026-42499)

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 rclone installed on the remote host is prior to 1.55.1-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-3309 advisory.

    Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS     if the meta tag also has an http-equiv attribute with the value refresh. A new GODEBUG setting has been     added, htmlmetacontenturlescape, which can be used to disable escaping URLs in actions in the meta content     attribute which follow url= by setting htmlmetacontenturlescape=0. (CVE-2026-27142)

    When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of     C memory and a crash. (CVE-2026-33811)

    When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION     frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0. (CVE-2026-33814)

    Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive     CPU exhaustion and memory allocations. (CVE-2026-39820)

    CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's     <content> attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the     <content> attribute, the escaper would fail to similarly escape it, leading to XSS. (CVE-2026-39823)

    Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC     5322. (CVE-2026-42499)

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.

ID	Name	Product	Family	Published	Updated	Severity
304588	Amazon Linux 2023 : runfinch-finch (ALAS2023-2026-1507)	Nessus	Amazon Linux Local Security Checks	4/1/2026	4/30/2026	medium
306272	Amazon Linux 2 : soci-snapshotter, --advisory ALAS2DOCKER-2026-107 (ALASDOCKER-2026-107)	Nessus	Amazon Linux Local Security Checks	4/14/2026	4/14/2026	critical
303295	SUSE SLES15 Security Update : go1.25-openssl (SUSE-SU-2026:0947-1)	Nessus	SuSE Local Security Checks	3/22/2026	3/22/2026	critical
316934	Amazon Linux 2 : cni-plugins, --advisory ALAS2-2026-3311 (ALAS-2026-3311)	Nessus	Amazon Linux Local Security Checks	5/27/2026	5/27/2026	high
316985	Amazon Linux 2 : rclone, --advisory ALAS2-2026-3309 (ALAS-2026-3309)	Nessus	Amazon Linux Local Security Checks	5/27/2026	5/27/2026	high

Detections

Analytics

Plugins Search

medium

critical

critical

high

high