Protection Mechanism Failure Affecting nuclei package, versions <3.4.2-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.27% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-WOLFILATEST-NUCLEI-15406329
  • published5 Mar 2026
  • disclosed20 Feb 2026

Introduced: 20 Feb 2026

CVE-2026-26994  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

Upgrade Wolfi nuclei to version 3.4.2-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nuclei package and not the nuclei package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

uTLS is a fork of crypto/tls, created to customize ClientHello for fingerprinting resistance while still using it for the handshake. In versions 1.6.7 and below, uTLS did not implement the TLS 1.3 downgrade protection mechanism specified in RFC 8446 Section 4.1.3 when using a uTLS ClientHello spec. This allowed an active network adversary to downgrade TLS 1.3 connections initiated by a uTLS client to a lower TLS version (e.g., TLS 1.2) by modifying the ClientHello message to exclude the SupportedVersions extension, causing the server to respond with a TLS 1.2 ServerHello (along with a downgrade canary in the ServerHello random field). Because uTLS did not check the downgrade canary in the ServerHello random field, clients would accept the downgraded connection without detecting the attack. This attack could also be used by an active network attacker to fingerprint uTLS connections. This issue has been fixed in version 1.7.0.