{"id":"GO-2025-3638","revision":null,"records":[{"revision":"b3f1d86f491943b7a565476fc82a5619","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-26994","aliases":[],"title":"uTLS ServerHellos are accepted without checking TLS 1.3 downgrade canaries","description":"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.","state":0,"publishedAt":"2026-02-20T02:50:18.439+00:00","modifiedAt":"2026-02-20T15:12:28.142+00:00","affected":[{"ecosystem":"Vendor product","name":"utls","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"refraction-networking\",\n                    \"product\": \"utls\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 1.7.0\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/refraction-networking/utls/security/advisories/GHSA-pmc3-p9hx-jq96","https://github.com/refraction-networking/utls/issues/181","https://github.com/refraction-networking/utls/pull/337","https://github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-26994","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-26994","identifiers":["CVE-2026-26994"]},"retained":false,"historicalAffected":[]},{"revision":"e6d0df170f464198b35e79ddd3761e09","observedAt":"2026-11-15T08:35:48.337+00:00","statement":{"source":"euvd","id":"EUVD-2026-8028","aliases":["CVE-2026-26994"],"title":"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…","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","score":6.5,"severity":null}],"references":["https://github.com/refraction-networking/utls/security/advisories/GHSA-pmc3-p9hx-jq96","https://github.com/refraction-networking/utls/issues/181","https://github.com/refraction-networking/utls/pull/337","https://github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-8028","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Feb 20, 2026, 2:50:18 AM","dateUpdated":"Feb 20, 2026, 3:12:28 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-8028","identifiers":["EUVD-2026-8028","CVE-2026-26994"]},"retained":false,"historicalAffected":[]},{"revision":"6e03251dd2d44d17ac980d53aa176c80","observedAt":"2026-10-25T06:17:28.833+00:00","statement":{"source":"nvd","id":"CVE-2026-26994","aliases":[],"title":"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…","description":"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.","state":0,"publishedAt":"2026-02-20T03:16:01.33+00:00","modifiedAt":"2026-06-17T10:26:30.4+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9","https://github.com/refraction-networking/utls/issues/181","https://github.com/refraction-networking/utls/pull/337","https://github.com/refraction-networking/utls/security/advisories/GHSA-pmc3-p9hx-jq96"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-26994","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Analyzed","weaknesses":["CWE-693"],"productCriteria":["cpe:2.3:a:refraction-networking:utls:*:*:*:*:*:go:*:*"],"sourceDates":{"published":"2026-02-20T03:16:01.330","lastModified":"2026-06-17T10:26:30.400"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2026-26994","identifiers":["CVE-2026-26994"]},"retained":false,"historicalAffected":[]},{"revision":"0b53a14a86424b89b32ab72fc5217c2f","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-pmc3-p9hx-jq96","aliases":["CVE-2026-26994","GO-2025-3638"],"title":"uTLS ServerHellos are accepted without checking TLS 1.3 downgrade canaries","description":"### Description\nBefore version 1.7.0, 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.\n\n### Fix Commit or Pull Request\n\nrefraction-networking/utls#337, specifically refraction-networking/utls@f8892761e2a4d29054264651d3a86fda83bc83f9\n\n### References\n\n- https://github.com/refraction-networking/utls/issues/181","state":0,"publishedAt":"2025-04-23T14:43:44+00:00","modifiedAt":"2026-09-10T03:50:23.9310036+00:00","affected":[{"ecosystem":"Go","name":"github.com/refraction-networking/utls","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.7.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/refraction-networking/utls/security/advisories/GHSA-pmc3-p9hx-jq96","https://nvd.nist.gov/vuln/detail/CVE-2026-26994","https://github.com/refraction-networking/utls/issues/181","https://github.com/refraction-networking/utls/pull/337","https://github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9","https://github.com/refraction-networking/utls"],"sourceUrl":"https://github.com/advisories/GHSA-pmc3-p9hx-jq96","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-pmc3-p9hx-jq96","identifiers":["GHSA-pmc3-p9hx-jq96","CVE-2026-26994","GO-2025-3638"]},"retained":false,"historicalAffected":[]},{"revision":"a3514b4a2b0c439f8f8c081e1d637b39","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2025-3638","aliases":["CVE-2026-26994","GHSA-pmc3-p9hx-jq96"],"title":"ServerHellos are accepted without checking TLS 1.3 downgrade canaries in github.com/refraction-networking/utls","description":"Before version 1.7.0, 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.","state":0,"publishedAt":"2025-04-24T18:13:59+00:00","modifiedAt":"2026-02-18T23:56:59.171282+00:00","affected":[{"ecosystem":"Go","name":"github.com/refraction-networking/utls","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"1.0.0"},{"kind":"fixed","version":"1.7.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/advisories/GHSA-pmc3-p9hx-jq96","https://github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9","https://github.com/refraction-networking/utls/pull/337","https://github.com/refraction-networking/utls/issues/181"],"sourceUrl":"https://osv.dev/vulnerability/GO-2025-3638","license":"OSV · upstream source license applies","key":"osv:GO-2025-3638","identifiers":["GO-2025-3638","CVE-2026-26994","GHSA-pmc3-p9hx-jq96"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-16T12:44:53.7069159+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T12:44:53.7069159+00:00","lastSuccessAt":"2026-11-16T12:44:53.850219+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.8502206+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-237c53704f95a87effe0a1147a1bcf3cd93376e65fa4303e1b86b3915f8b7c7a","complete":true,"records":425970,"lastAttemptAt":"2026-11-16T12:44:53.412921+00:00","lastSuccessAt":"2026-11-16T12:44:53.3189092+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.412921+00:00","snapshotPublishedAt":"2026-11-16T12:28:00+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-ea8954ba9b8a4f759f7e51e8bc4698ca","complete":false,"records":13821,"lastAttemptAt":"2026-11-16T12:46:28.5866342+00:00","lastSuccessAt":"2026-11-16T12:46:28.582+00:00","error":"5 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T12:46:28.582+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13869,"expectedIdentifiers":13874,"failedIdentifiers":5},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-16T12:44:53.7069159+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T12:44:53.7069159+00:00","lastSuccessAt":"2026-11-16T12:44:53.8509796+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.85098+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-1ca26f249fe448ada48a3a7b82aa64d9","complete":false,"records":13833,"lastAttemptAt":"2026-11-16T12:45:56.1167563+00:00","lastSuccessAt":"2026-11-16T12:45:56.113+00:00","error":"400 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T12:45:56.113+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13474,"expectedIdentifiers":13874,"failedIdentifiers":400},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T12:44:53.6598825+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.6598825+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-16T12:44:53.4548081+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.4548081+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T12:44:53.6730048+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.6730048+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-263d9c8d63997345727b11314d9b9377eba9fd4146f04497c069a15e332b60cb","complete":true,"records":232482,"lastAttemptAt":"2026-11-16T12:44:53.5565665+00:00","lastSuccessAt":"2026-11-16T07:32:30.5701252+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.5565665+00:00","snapshotPublishedAt":"2026-11-16T06:48:00+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}