Vulnerability Database · Go · Package report
github.com/mdlayher/vsock: vulnerability history, versions and safety
github.com/mdlayher/vsock 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/mdlayher/vsock v1.3.0 i
Updated on 23 Oct 2026
Good news: v1.3.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v1.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.3.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 396 i
- OpenSSF scorecard 4/10 i
- Last release 4 months ago i
- Licence MIT 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/mdlayher/vsock, 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.
- v1.3.1-0.20261015071119-7a4dcaeb0d7a 15 Oct 2026
- v1.3.1-0.20261015070939-f5b7edf7b946 15 Oct 2026
- v0.0.0-20260526064718-ffafd72337a0 26 May 2026
- v1.3.0 26 May 2026
- v1.2.2-0.20250106181908-908db2f631ff 06 Jan 2025
- v1.2.2-0.20230823131721-068aff8a5e29 23 Aug 2023
- v1.2.2-0.20230429142655-76b624c2c881 29 Apr 2023
- v1.2.1 29 Apr 2023
- v0.0.0-20221112163721-051f33a49647 12 Nov 2022
- v1.2.0 12 Nov 2022
- v1.1.1 19 Feb 2022
- v1.1.1-0.20220219213856-ead86435c244 19 Feb 2022
- v1.1.1-0.20220219211554-0a7673e9023b 19 Feb 2022
- v1.1.0 12 Feb 2022
- v1.0.2-0.20220211184804-099435de881c 11 Feb 2022
- v1.0.1 11 Feb 2022
- v1.0.1-0.20220205131902-375f3bbcc363 05 Feb 2022
- v0.0.0-20220204201116-bbe4f973c57e 04 Feb 2022
- v1.0.0 04 Feb 2022
- v0.0.0-20220204195230-e43ee04760c8 04 Feb 2022
- v0.0.0-20220204191218-4cca7b0e0855 04 Feb 2022
- v0.0.0-20220204191159-d9bdd618803e 04 Feb 2022
- v0.0.0-20220204172642-101af49e8b76 04 Feb 2022
- v0.0.0-20211216193947-a12ffa19abdd 16 Dec 2021
- v0.0.0-20211215210649-606317894389 15 Dec 2021
- v0.0.0-20210303205602-10d591861736 03 Mar 2021
- v0.0.0-20210228210306-27f4a37e7dc0 28 Feb 2021
- v0.0.0-20210228164928-3c221e0476e2 28 Feb 2021
- v0.0.0-20200508120832-7ad3638b3fbc 08 May 2020
- v0.0.0-20191108225356-d9c65923cb8f 08 Nov 2019
- v0.0.0-20191108225300-e22a05b701d9 08 Nov 2019
- v0.0.0-20191108224102-318071cce8eb 08 Nov 2019
- v0.0.0-20191107082414-b389f0108a09 07 Nov 2019
- v0.0.0-20191107081732-1f7f4e4beb4c 07 Nov 2019
- v0.0.0-20190516140846-9de589a8c10b 16 May 2019
- v0.0.0-20190509154515-25f26bbd0fea 09 May 2019
- v0.0.0-20190429153235-7b7533a7ca4e 29 Apr 2019
- v0.0.0-20190403160522-7746c149d44a 03 Apr 2019
- v0.0.0-20190329173812-a92c53d5dcab 29 Mar 2019
- v0.0.0-20190329141806-4be9c507fde1 29 Mar 2019
- v0.0.0-20190329141344-11d3b17d9d31 29 Mar 2019
- v0.0.0-20190329033602-3f30162f3c4e 29 Mar 2019
- v0.0.0-20190326130659-1ce6a21ee7c7 26 Mar 2019
- v0.0.0-20190322043915-272e6fe2d4c5 22 Mar 2019
- v0.0.0-20190321215815-7e331fac06df 21 Mar 2019
- v0.0.0-20190321215714-e48d7efa6dd4 21 Mar 2019
- v0.0.0-20190319125627-33f548ae9d30 19 Mar 2019
- v0.0.0-20190318224515-4b4b46fb16ba 18 Mar 2019
- v0.0.0-20190318182242-cbbd08d541be 18 Mar 2019
- v0.0.0-20190318142349-732b590f5c71 18 Mar 2019
- v0.0.0-20190316174044-a4d81bedbf02 16 Mar 2019
- v0.0.0-20190315212355-86190a6f8b27 15 Mar 2019
- v0.0.0-20190315163633-4e70ebb94e89 15 Mar 2019
- v0.0.0-20190315022103-144e12645594 15 Mar 2019
- v0.0.0-20181130155850-676f733b747c 30 Nov 2018
- v0.0.0-20181109184530-4b12813d3604 09 Nov 2018
- v0.0.0-20180806202057-2b18bec03226 06 Aug 2018
- v0.0.0-20180805150941-7a158c6fbe3a 05 Aug 2018
- v0.0.0-20180730212259-097671395fb7 30 Jul 2018
- v0.0.0-20180730212056-f68ad5598dc6 30 Jul 2018
- v0.0.0-20180713175216-65587aa3274a 13 Jul 2018
- v0.0.0-20171201161058-738c88d6e4cf 01 Dec 2017
- v0.0.0-20171123170625-7b5c6741e074 23 Nov 2017
- v0.0.0-20171107160816-264f864f8aa4 07 Nov 2017
- v0.0.0-20170601210414-262158c24407 01 Jun 2017
- v0.0.0-20170503042527-23405a4fb2cd 03 May 2017
- v0.0.0-20170413181309-225894148569 13 Apr 2017
- v0.0.0-20170310162543-731f7686d5c9 10 Mar 2017
All 68 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/mdlayher/vsock
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/mdlayher/vsock
Is github.com/mdlayher/vsock safe to use?
Vulert has no vulnerabilities on record for github.com/mdlayher/vsock 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/mdlayher/vsock's Vulert package health score?
Vulert scores github.com/mdlayher/vsock 71/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/mdlayher/vsock affected?
No. v1.3.0, 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/mdlayher/vsock should I use?
v1.3.0 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/mdlayher/vsock have?
0 vulnerabilities are recorded for github.com/mdlayher/vsock 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/mdlayher/vsock vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mdlayher/vsock 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/mdlayher/vsock 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/mdlayher/vsock for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mdlayher/vsock version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.