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

    SSH Agent servers do not validate the size of messages when processing new identity requests, which may     cause the program to panic if the message is malformed due to an out of bounds read. (CVE-2025-47914)

    SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in     the request, allowing an attacker to cause unbounded memory consumption. (CVE-2025-58181)

    crypto/x509: excluded subdomain constraint does not restrict wildcard SANs

    An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in     the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not     prevent a leaf certificate from claiming the SAN *.example.com. (CVE-2025-61727)

    Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts     that will be printed out. Furthermore, the error string is constructed by repeated string concatenation,     leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in     excessive resource consumption. (CVE-2025-61729)

    Fulcio is a free-to-use certificate authority for issuing code signing certificates for an OpenID Connect     (OIDC) identity. Prior to 1.8.3, function identity.extractIssuerURL splits (via a call to strings.Split)     its argument (which is untrusted data) on periods. As a result, in the face of a malicious request with an     (invalid) OIDC identity token in the payload containing many period characters, a call to extractIssuerURL     incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument),     with a constant factor of about 16. This vulnerability is fixed in 1.8.3. (CVE-2025-66506)

    Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function     api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is     untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which     is also untrusted data) on an application string. As a result, in the face of a malicious request with     either an excessively long OID in the payload containing many period characters or a malformed Content-     Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where     n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.
    (CVE-2025-66564)

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 openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:20191-1 advisory.

    Changes in trivy:

    - Update to version 0.69.0 (bsc#1255366, CVE-2025-64702):
      * release: v0.69.0 [main] (#9886)
      * chore: bump trivy-checks to v2 (#9875)
      * chore(deps): bump github.com/theupdateframework/go-tuf/v2 from 2.3.1 to 2.4.1 (#10091)
      * fix(repo): return a nil interface for gitAuth if missing (#10097)
      * fix(java): correctly inherit properties from parent fields for pom.xml files (#9111)
      * fix(rust): implement version inheritance for Cargo mono repos (#10011)
      * feat(activestate): add support ActiveState images (#10081)
      * feat(vex): support per-repo tls configuration (#10030)
      * refactor: allow per-request transport options override (#10083)
      * chore(deps): bump github.com/sigstore/rekor from 1.4.3 to 1.5.0 (#10084)
      * chore(deps): bump github.com/sigstore/sigstore from 1.10.3 to 1.10.4 (#10085)
      * fix(java): correctly propagate repositories from upper POMs to dependencies (#10077)
      * feat(rocky): enable modular package vulnerability detection (#10069)
      * chore(deps): bump github.com/theupdateframework/go-tuf/v2 from 2.3.0 to 2.3.1 (#10079)
      * docs: fix mistake in config file example for skip-dirs/skip-files flag (#10070)
      * feat(report): add Trivy version to JSON output (#10065)
      * fix(rust): add cargo workspace members glob support (#10032)
      * feat: add AnalyzedBy field to track which analyzer detected packages (#10059)
      * fix: use canonical SPDX license IDs from embeded licenses.json (#10053)
      * docs: fix link to Docker Image Specification (#10057)
      * feat(secret): add detection for Symfony default secret key (#9892)
      * refactor(misconf): move common logic to base value and simplify typed values (#9986)
      * fix(java): add hash of GAV+root pom file path for pkgID for packages from pom.xml files (#9880)
      * feat(misconf): use Terraform plan configuration to partially restore schema (#9623)
      * feat(misconf): add action block to Terraform schema (#10035)
      * fix(misconf): correct typos in block and attribute names (#9993)
      * test(misconf): simplify test values using *Test helpers (#9985)
      * fix(misconf): safely parse rotation_period in google_kms_crypto_key (#9980)
      * feat(misconf): support for ARM resources defined as an object (#9959)
      * feat(misconf): support for azurerm_*_web_app (#9944)
      * test: migrate private test helpers to `export_test.go` convention (#10043)
      * chore(deps): bump github.com/sigstore/cosign/v2 from 2.2.4 to 2.6.2 (#10048)
      * fix(secret): improve word boundary detection for Hugging Face tokens (#10046)
      * fix(go): use ldflags version for all pseudo-versions    (#10037)
      * chore: switch to ID from AVDID in internal and user-facing fields (#9655)
      * refactor(misconf)!: use ID instead of AVDID for providers mapping (#9752)
      * fix: move enum into items for array-type fields in JSON Schema (#10039)
      * docs: fix incorrect documentation URLs (#10038)
      * feat(sbom): exclude PEP 770 SBOMs in .dist-info/sboms/ (#10033)
      * fix(docker): fix non-det scan results for images with embedded SBOM (#9866)
      * chore(deps): bump the github-actions group with 11 updates (#10001)
      * test: fix assertion after 2026 roll over (#10002)
      * fix(vuln): skip vulns detection for CentOS Stream family without scan failure (#9964)
      * fix(license): normalize licenses for PostAnalyzers (#9941)
      * feat(nodejs): parse licenses from `package-lock.json` file (#9983)
      * chore: update reference links to Go Wiki (#9987)
      * refactor: add xslices.Map and replace lo.Map usages (#9984)
      * fix(image): race condition in image artifact inspection (#9966)
      * feat(flag): add JSON Schema for trivy.yaml configuration file (#9971)
      * refactor(debian): use txtar format for test data (#9957)
      * chore(deps): bump `golang.org/x/tools` to `v0.40.0` + `gopls` to `v0.21.0` (#9973)
      * feat(rootio): Update trivy db to support usage of Severity from root.io feed (#9930)
      * feat(vuln): skip vulnerability scanning for third-party packages in Debian/Ubuntu (#9932)
      * docs: add info that `--file-pattern` flag doesn't disable default behaviuor (#9961)
      * perf(misconf): optimize string concatenation in azure scanner (#9969)
      * chore: add client option to install script (#9962)
      * ci(helm): bump Trivy version to 0.68.2 for Trivy Helm Chart 0.20.1 (#9956)
      * chore(deps): bump github.com/quic-go/quic-go from 0.54.1 to 0.57.0 (#9952)
      * docs: update binary signature verification for sigstore bundles (#9929)
      * chore(deps): bump alpine from `3.22.1` to `3.23.0` (#9935)
      * chore(alpine): add EOL date for alpine 3.23 (#9934)
      * feat(cloudformation): add support for Fn::ForEach (#9508)
      * ci: enable `check-latest` for `setup-go` (#9931)
      * feat(debian): detect third-party packages using maintainer list (#9917)
      * fix(vex): add CVE-2025-66564 as not_affected into Trivy VEX file (#9924)
      * feat(helm): add sslCertDir parameter (#9697)
      * fix(misconf): respect .yml files when Helm charts are detected (#9912)
      * feat(php): add support for dev dependencies in Composer (#9910)
      * chore(deps): bump the common group across 1 directory with 9 updates (#9903)
      * chore(deps): bump github.com/docker/cli from 29.0.3+incompatible to 29.1.1+incompatible in the docker     group (#9859)
      * fix: remove trailing tab in statefulset template (#9889)
      * feat(julia): enable vulnerability scanning for the Julia language ecosystem (#9800)
      * feat(misconf): initial ansible scanning support (#9332)
      * feat(misconf): Update Azure Database schema (#9811)
      * ci(helm): bump Trivy version to 0.68.1 for Trivy Helm Chart 0.20.0 (#9869)
      * chore: update the install script (#9874)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function     api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is     untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which     is also untrusted data) on an application string. As a result, in the face of a malicious request with     either an excessively long OID in the payload containing many period characters or a malformed Content-     Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where     n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.
    (CVE-2025-66564)

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

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

    SSH Agent servers do not validate the size of messages when processing new identity requests, which may     cause the program to panic if the message is malformed due to an out of bounds read. (CVE-2025-47914)

    SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in     the request, allowing an attacker to cause unbounded memory consumption. (CVE-2025-58181)

    crypto/x509: excluded subdomain constraint does not restrict wildcard SANs

    An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in     the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not     prevent a leaf certificate from claiming the SAN *.example.com. (CVE-2025-61727)

    Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts     that will be printed out. Furthermore, the error string is constructed by repeated string concatenation,     leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in     excessive resource consumption. (CVE-2025-61729)

    Fulcio is a free-to-use certificate authority for issuing code signing certificates for an OpenID Connect     (OIDC) identity. Prior to 1.8.3, function identity.extractIssuerURL splits (via a call to strings.Split)     its argument (which is untrusted data) on periods. As a result, in the face of a malicious request with an     (invalid) OIDC identity token in the payload containing many period characters, a call to extractIssuerURL     incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument),     with a constant factor of about 16. This vulnerability is fixed in 1.8.3. (CVE-2025-66506)

    Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function     api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is     untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which     is also untrusted data) on an application string. As a result, in the face of a malicious request with     either an excessively long OID in the payload containing many period characters or a malformed Content-     Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where     n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.
    (CVE-2025-66564)

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 Fedora 42 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-de52e7caa1 advisory.

    Update to 2.87.3

Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 44 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-6b87863841 advisory.

    Upstream release 2.98.0. https://github.com/jfrog/jfrog-cli/releases/tag/v2.98.0

    Resolves the following security issues:
    CVE-2025-11579     CVE-2025-66564     CVE-2026-23831     CVE-2026-23991     CVE-2026-23992     CVE-2026-24117     CVE-2026-24137     CVE-2026-24686     CVE-2026-32285     CVE-2026-33762     CVE-2026-34165     CVE-2026-34986

Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 43 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-868e266938 advisory.

    Update to 0.69.3

Tenable has extracted the preceding description block directly from the Fedora 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
282402	Amazon Linux 2023 : runfinch-finch (ALAS2023-2025-1336)	Nessus	Amazon Linux Local Security Checks	1/8/2026	2/24/2026	medium
298721	openSUSE 16 Security Update : trivy (openSUSE-SU-2026:20191-1)	Nessus	SuSE Local Security Checks	2/12/2026	2/12/2026	high
277673	Linux Distros Unpatched Vulnerability : CVE-2025-66564	Nessus	Misc.	12/8/2025	4/29/2026	high
281772	Amazon Linux 2 : runfinch-finch, --advisory ALAS2DOCKER-2025-092 (ALASDOCKER-2025-092)	Nessus	Amazon Linux Local Security Checks	1/5/2026	2/24/2026	medium
301422	Fedora 42 : gh (2026-de52e7caa1)	Nessus	Fedora Local Security Checks	3/7/2026	3/7/2026	high
311385	Fedora 44 : jfrog-cli (2026-6b87863841)	Nessus	Fedora Local Security Checks	5/1/2026	5/1/2026	high
306074	Fedora 43 : trivy (2026-868e266938)	Nessus	Fedora Local Security Checks	4/13/2026	4/13/2026	high

Detections

Analytics

Plugins Search

medium

high

high

medium

high

high

high