uTLS is a fork of crypto/tls, created to customize ClientHello for fingerprinting resistance while still using it for the handshake. Versions 1.6.0 through 1.8.0 contain a fingerprint mismatch with Chrome when using GREASE ECH, related to cipher suite selection. When Chrome selects the preferred cipher suite in the outer ClientHello and for ECH, it does so consistently based on hardware support—for example, if it prefers AES for the outer cipher suite, it also uses AES for ECH. However, the Chrome parrot in uTLS hardcodes AES preference for outer cipher suites but selects the ECH cipher suite randomly between AES and ChaCha20. This creates a 50% chance of selecting ChaCha20 for ECH while using AES for the outer cipher suite, a combination impossible in Chrome. This issue only affects GREASE ECH; in real ECH, Chrome selects the first valid cipher suite when AES is preferred, which uTLS handles correctly. This issue has been fixed in version 1.8.1.

The remote openSUSE 16 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21653-1 advisory.

    Changes in v2ray-core:

    - Update version to 5.53.0
      * Add X-Forwarded-For support to gRPC transport
      * Add Stream based Packet Addr for UDP Connections
      * rrpit: compact session, async send, session recovery
      * Add socks5ify engineering command
      * Fix bugs
      * Update modules (boo#1276119 and CVE-2026-72817, CVE-2026-72815, CVE-2026-72816)

    - Update version to 5.51.2
      * Wireguard Add TCP Listener support for wireguard outbound
      * Stun Nat Type Testing
      * Better server failure detection and PreserveSourceIPPortWhenDestNATMapping         detection
      * Improve API instance support
      * feat: grpc: allow configurable keepalive and initial windows size
      * Add RRPIT - Rapid Reliable Packet Interactive Transport
      * Add WebRTC Tunnel Support in V2Ray(unreleased)
      * also parse X-Forwarded-For in httpupgrade
      * gdocsviewer: Add Google Docs Viewer based transport
      * gdocsviewer: Refine poll logic and allow custom headers to reduce rate limiting
      * gdocsviewer: allow adding headers in public config
      * Fix bugs (boo#1258546 and CVE-2026-27017)

    - update golang.org/x/net to 0.55.0 to fix boo#1266787 and CVE-2026-39821

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.

  - uTLS is a fork of crypto/tls, created to customize ClientHello for fingerprinting resistance while still     using it for the handshake. Versions 1.6.0 through 1.8.0 contain a fingerprint mismatch with Chrome when     using GREASE ECH, related to cipher suite selection. When Chrome selects the preferred cipher suite in the     outer ClientHello and for ECH, it does so consistently based on hardware supportfor example, if it     prefers AES for the outer cipher suite, it also uses AES for ECH. However, the Chrome parrot in uTLS     hardcodes AES preference for outer cipher suites but selects the ECH cipher suite randomly between AES and     ChaCha20. This creates a 50% chance of selecting ChaCha20 for ECH while using AES for the outer cipher     suite, a combination impossible in Chrome. This issue only affects GREASE ECH; in real ECH, Chrome selects     the first valid cipher suite when AES is preferred, which uTLS handles correctly. This issue has been     fixed in version 1.8.1. (CVE-2026-27017)

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

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - uTLS is a fork of crypto/tls, created to customize ClientHello for fingerprinting resistance while still
    using it for the handshake. Versions 1.6.0 through 1.8.0 contain a fingerprint mismatch with Chrome when
    using GREASE ECH, related to cipher suite selection. When Chrome selects the preferred cipher suite in the
    outer ClientHello and for ECH, it does so consistently based on hardware support—for example, if it
    prefers AES for the outer cipher suite, it also uses AES for ECH. However, the Chrome parrot in uTLS
    hardcodes AES preference for outer cipher suites but selects the ECH cipher suite randomly between AES and
    ChaCha20. This creates a 50% chance of selecting ChaCha20 for ECH while using AES for the outer cipher
    suite, a combination impossible in Chrome. This issue only affects GREASE ECH; in real ECH, Chrome selects
    the first valid cipher suite when AES is preferred, which uTLS handles correctly. This issue has been
    fixed in version 1.8.1. (CVE-2026-27017)

ID	Name	Product	Family	Type	Severity
341167	openSUSE 16 Security Update : v2ray-core (openSUSE-SU-2026:21653-1)	Nessus	SuSE Local Security Checks	Local	medium
299829	Linux Distros Unpatched Vulnerability : CVE-2026-27017	Nessus	Misc.	Local	low
437849	SCA: security update for github.com/refraction-networking/utls (GHSA-7m29-f4hw-g2vx)	Tenable Cloud Security	SCA Checks	Local	low
437849	SCA: security update for github.com/refraction-networking/utls (GHSA-7m29-f4hw-g2vx)	Tenable Self-Hosted Container Security	SCA Checks	Local	low

Detections

Analytics

CVE-2026-27017

low

Tenable Plugins

medium

low

low

low