Vulnerability Database · Go · Package report

github.com/linuxkit/virtsock: vulnerability history, versions and safety

github.com/linuxkit/virtsock is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/linuxkit/virtsock v0.0.0-20241009230534-cb6a20cc0422 i

Updated on 23 Oct 2026

Good news: v0.0.0-20241009230534-cb6a20cc0422, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

What to do: Stay on v0.0.0-20241009230534-cb6a20cc0422 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20241009230534-cb6a20cc0422 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.0.0-20241009230534-cb6a20cc0422 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 94 i
  • OpenSSF scorecard 1/10 i
  • Last release 24 months ago i
  • Licence Apache-2.0 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/linuxkit/virtsock, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20241009230534-cb6a20cc0422 09 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20241009213439-19af90827e70 09 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20220523201153-1a23e78aa7a2 23 May 2022 none Apache-2.0 — Details →
v0.0.0-20220522141644-a57a6fd243d3 22 May 2022 none Apache-2.0 — Details →
v0.0.0-20220326174755-1c88ab3ae042 26 Mar 2022 none Apache-2.0 — Details →
v0.0.0-20220326163212-27abaf08f0cd 26 Mar 2022 none Apache-2.0 — Details →
v0.0.0-20201010232012-f8cee7dfc7a3 10 Oct 2020 none Apache-2.0 — Details →
v0.0.0-20200904092844-5d374c8e10aa 04 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20180830132707-8e79449dea07 30 Aug 2018 none Apache-2.0 — Details →
v0.0.0-20180829101611-ab3a01224dbb 29 Aug 2018 none Apache-2.0 — Details →
v0.0.0-20180411161033-76c5cbe7912f 11 Apr 2018 none Apache-2.0 — Details →
v0.0.0-20180323111827-f1e32d3189e0 23 Mar 2018 none Apache-2.0 — Details →
v0.0.0-20180323110630-b95cf8069993 23 Mar 2018 none Apache-2.0 — Details →
v0.0.0-20180214172400-2e14095e6416 14 Feb 2018 none Apache-2.0 — Details →
v0.0.0-20180209104145-1cc8fd7aa101 09 Feb 2018 none Apache-2.0 — Details →
v0.0.0-20180208153509-a618f791cdf1 08 Feb 2018 none Apache-2.0 — Details →
v0.0.0-20180208140506-95a615631f99 08 Feb 2018 none Apache-2.0 — Details →
v0.0.0-20180202171659-db93468a3edb 02 Feb 2018 none Apache-2.0 — Details →
v0.0.0-20180131164723-08d3ba99f049 31 Jan 2018 none Apache-2.0 — Details →
v0.0.0-20180131164723-0aebb57fceac 31 Jan 2018 none Apache-2.0 — Details →
v0.0.0-20180131164723-94134227fa88 31 Jan 2018 none Apache-2.0 — Details →
v0.0.0-20171214164431-cffdef077e42 14 Dec 2017 none Apache-2.0 — Details →
v0.0.0-20171214152308-16526721cfbf 14 Dec 2017 none Apache-2.0 — Details →
v0.0.0-20171117111855-16fb39ea6df1 17 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20171116110800-95948258470b 16 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20171115174133-0846ed5fea1b 15 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20170914101008-cce5df4cc3fb 14 Sep 2017 none Apache-2.0 — Details →
v0.0.0-20170914092441-430d7b4523e5 14 Sep 2017 none Apache-2.0 — Details →
v0.0.0-20170908164546-546c693f86e7 08 Sep 2017 none Apache-2.0 — Details →
v0.0.0-20170904163137-40afd9143f99 04 Sep 2017 none Apache-2.0 — Details →
v0.0.0-20170720150838-0416e3d85541 20 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170714155755-43eb0bb643ce 14 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170714153746-a4c8c0e14d8c 14 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170712204329-2d567dc8b2d3 12 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170710204222-06e97e8056a4 10 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170709172425-74347e25f80d 09 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170707140326-298d0178dbea 07 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170707005059-8673ecb0ac89 07 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170703181640-4cf888f941ae 03 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170703135053-389d531d65b8 03 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170703135053-7d4b3e5f88b6 03 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170703125829-762e85c7c864 03 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170630185929-0ee7fbad7a78 30 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170609120700-d8602200812a 09 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170608134402-b40e3bc4505a 08 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170602135331-a381dcc5bcdd 02 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170602113346-1df8ba80a774 02 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170515135651-366671b2c7fe 15 May 2017 none Apache-2.0 — Details →
v0.0.0-20170512143158-313793babff9 12 May 2017 none Apache-2.0 — Details →
v0.0.0-20170511104948-2a9e846875a0 11 May 2017 none Apache-2.0 — Details →
v0.0.0-20170511092705-01cbddaa1617 11 May 2017 none Apache-2.0 — Details →
v0.0.0-20170509135152-06165fbd87ef 09 May 2017 none Apache-2.0 — Details →
v0.0.0-20170321174638-4c486dad9d3b 21 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170208170015-31cb2ce4ce79 08 Feb 2017 none Apache-2.0 — Details →
v0.0.0-20170130152813-7ccae9dd438d 30 Jan 2017 none Apache-2.0 — Details →
v0.0.0-20161218182856-3175da3d233a 18 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161217161516-2fd40a72cac1 17 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161216103312-287214eed84d 16 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161215164742-210196297bca 15 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161213152730-22a7584217c5 13 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161212150453-1ef17cd907f1 12 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161210151823-420498a285d4 10 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161122151919-0db9a74956b9 22 Nov 2016 none Apache-2.0 — Details →
v0.0.0-20160623111612-650ef8224a0c 23 Jun 2016 none Apache-2.0 — Details →
v0.0.0-20160615095930-0e2f0a87b1af 15 Jun 2016 none Apache-2.0 — Details →
v0.0.0-20160517165121-0a33cb243f59 17 May 2016 none Apache-2.0 — Details →
v0.0.0-20160513164149-08f212fa6029 13 May 2016 none Apache-2.0 — Details →
v0.0.0-20160408140810-b0b00673905e 08 Apr 2016 none — — Details →

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/linuxkit/virtsock

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/linuxkit/virtsock

Is github.com/linuxkit/virtsock safe to use?

Vulert has no vulnerabilities on record for github.com/linuxkit/virtsock 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/linuxkit/virtsock's Vulert package health score?

Vulert scores github.com/linuxkit/virtsock 61/100, which reads as usable, but worth attention. 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/linuxkit/virtsock affected?

No. v0.0.0-20241009230534-cb6a20cc0422, 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/linuxkit/virtsock should I use?

v0.0.0-20241009230534-cb6a20cc0422 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/linuxkit/virtsock have?

0 vulnerabilities are recorded for github.com/linuxkit/virtsock 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/linuxkit/virtsock vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/linuxkit/virtsock 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/linuxkit/virtsock 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/linuxkit/virtsock for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/linuxkit/virtsock version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.