Vulnerability Database · Go · Package report
github.com/metacubex/utls: vulnerability history, versions and safety
github.com/metacubex/utls is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/metacubex/utls v1.8.8 i
Updated on 23 Oct 2026
Good news: v1.8.8, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.8.8 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.8.8 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.8.8 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 8 i
- Last release this month i
- Licence BSD-3-Clause i
Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/metacubex/utls, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- v0.0.0-20261013160100-8853e107ae26 13 Oct 2026
- v0.0.0-20261011131148-d4150a6c7c06 11 Oct 2026
- v1.8.8 30 Sep 2026
- v0.0.0-20260930132604-78c9290bf587 30 Sep 2026
- v0.0.0-20260924074610-04010625d68b 24 Sep 2026
- v0.0.0-20260726054410-2aa631698733 26 Jul 2026
- v1.8.8-0.20260726052843-7adb2156aad6 26 Jul 2026
- v1.8.8-0.20260716151218-edd28c4bdde5 16 Jul 2026
- v0.0.0-20260715025833-a77524af3a17 15 Jul 2026
- v1.8.8-0.20260714021731-2d03e0b59a75 14 Jul 2026
- v0.0.0-20260709025642-7f3c5a57c88c 09 Jul 2026
- v1.8.7 26 Jun 2026
- v1.8.6 26 Jun 2026
- v1.8.5 26 Jun 2026
- v0.0.0-20260312170409-baeb46d2f908 12 Mar 2026
- v1.8.5-0.20260305145217-c2bf685c287c 05 Mar 2026
- v1.8.4 13 Jan 2026
- v1.8.3 18 Oct 2025
- v1.8.2 14 Oct 2025
- v1.8.2-0.20250924125012-475deebf819f 24 Sep 2025
- v1.8.1 24 Sep 2025
- v1.8.1-0.20250923145048-0a5bbc90dd3e 23 Sep 2025
- v1.8.1-0.20250923144113-2bac63ebb578 23 Sep 2025
- v1.8.1-0.20250923140010-e9ee456e33f7 23 Sep 2025
- v1.8.1-0.20250923135100-82a67cb8e6fc 23 Sep 2025
- v1.8.1-0.20250923125213-9c6fd2a4cfaf 23 Sep 2025
- v1.8.1-0.20250923100002-5915f4ac9c16 23 Sep 2025
- v1.8.1-0.20250923095929-5a5baffa4b76 23 Sep 2025
- v1.8.1-0.20250923093220-ae8f15a2f1d1 23 Sep 2025
- v1.8.1-0.20250923084142-4a126b408387 23 Sep 2025
- v1.8.1-0.20250923075840-4fe627c02a80 23 Sep 2025
- v1.8.1-0.20250921102910-221428e5d4b2 21 Sep 2025
- v1.8.1-0.20250916021850-3fcad0728a32 16 Sep 2025
- v1.8.1-0.20250823120917-12f5ba126142 23 Aug 2025
- v1.8.1-0.20250811145843-49b4f106169a 11 Aug 2025
- v1.8.1-0.20250810142204-d0e55ab2e852 10 Aug 2025
- v1.7.4-0.20250722064141-8b5753f5737a 22 Jul 2025
- v1.8.0 22 Jul 2025
- v1.7.4-0.20250722061954-3bf9da70d31e 22 Jul 2025
- v1.7.4-0.20250721031632-0231e2af7f3a 21 Jul 2025
- v1.7.4-0.20250628044047-8d330f8b93bf 28 Jun 2025
- v1.7.4-0.20250610022031-808d767c8c73 10 Jun 2025
- v1.7.3 15 May 2025
- v1.7.0-alpha.3 09 May 2025
- v1.7.0-alpha.1.0.20250503031404-9e929954c826 03 May 2025
- v1.7.0-alpha.2 03 May 2025
- v1.7.0-alpha.1 21 Apr 2025
- v1.6.8-alpha.6 12 Apr 2025
- v1.6.8-alpha.5 12 Apr 2025
- v1.6.8-alpha.4 18 Mar 2025
- v1.6.8-alpha.2 18 Mar 2025
- v0.0.0-20250220031855-8a87ce02366b 20 Feb 2025
- v1.6.8-alpha.1 20 Feb 2025
- v0.0.0-20240519024618-63e835d02e8e 19 May 2024
- v1.6.6 19 May 2024
All 55 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for github.com/metacubex/utls
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About github.com/metacubex/utls
Is github.com/metacubex/utls safe to use?
Vulert has no vulnerabilities on record for github.com/metacubex/utls in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/metacubex/utls's Vulert package health score?
Vulert scores github.com/metacubex/utls 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of github.com/metacubex/utls affected?
No. v1.8.8, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/metacubex/utls should I use?
v1.8.8 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does github.com/metacubex/utls have?
0 vulnerabilities are recorded for github.com/metacubex/utls in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new github.com/metacubex/utls vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/metacubex/utls in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of github.com/metacubex/utls are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor github.com/metacubex/utls for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/metacubex/utls version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.