VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/moby/ipvs: vulnerability history, versions and safety

github.com/moby/ipvs 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.

See all github.com/moby/ipvs vulnerabilities

Vulert verdict on github.com/moby/ipvs v1.1.0 i

Updated on 23 Oct 2026

Good news: v1.1.0, the version you would install today, has no known vulnerabilities.

Package health score 58/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release v1.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 110 i
  • OpenSSF scorecard 3/10 i
  • Last release 45 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/moby/ipvs, 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
v1.1.1-0.20261015205243-42b48392135b 15 Oct 2026 none Apache-2.0 — Details →
v1.1.1-0.20261014154123-21a72d0df817 14 Oct 2026 none Apache-2.0 — Details →
v1.1.1-0.20261013144753-b2c39ffcfc6f 13 Oct 2026 none Apache-2.0 — Details →
v1.1.1-0.20261011184324-fc590b8e2748 11 Oct 2026 none Apache-2.0 — Details →
v1.1.1-0.20261009111238-d8e1ca3af464 09 Oct 2026 none Apache-2.0 — Details →
v0.0.0-20230114155403-fe22ac585b3e 14 Jan 2023 none Apache-2.0 — Details →
v1.1.0 14 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230114152227-0129b48ee3b7 14 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230114134627-2f31a04506c6 14 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230114133705-04a86f9d5881 14 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230113134317-d2a9113db497 13 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230112141432-624d3f53f5d6 12 Jan 2023 none Apache-2.0 — Details →
v1.0.2 31 May 2022 none Apache-2.0 — Details →
v1.0.2-0.20220530184506-dc83eb7660d6 30 May 2022 none Apache-2.0 — Details →
v1.0.2-0.20200430144732-d5d89bed3438 30 Apr 2020 none Apache-2.0 — Details →
v0.0.0-20200428142043-4566ccea0e08 28 Apr 2020 none Apache-2.0 — Details →
v1.0.1 28 Apr 2020 none Apache-2.0 — Details →
v1.0.1-0.20200427192859-065f6ad2ff81 27 Apr 2020 none Apache-2.0 — Details →
v1.0.1-0.20200427145309-35400b9bf067 27 Apr 2020 none Apache-2.0 — Details →
v1.0.1-0.20200331193101-80776c331f6d 31 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200312125647-8f137da6850a 12 Mar 2020 none Apache-2.0 — Details →
v1.0.0 12 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200312125411-2b97f91f5793 12 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200312121906-a4aa101a48f5 12 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200311213924-6907374b1ec4 11 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20180913162003-9f9d138b211a 13 Sep 2018 none — — Details →
v0.0.0-20180712195444-8d6ff060f49d 12 Jul 2018 none — — Details →
v0.0.0-20171025133306-3af220a2b066 25 Oct 2017 none — — Details →
v0.0.0-20170807182047-cab8425421ed 07 Aug 2017 none — — Details →
v0.0.0-20170524022659-25929e9b4a6f 24 May 2017 none — — Details →
v0.0.0-20170519202944-158bd4ae834b 19 May 2017 none — — Details →
v0.0.0-20170207063111-5ec55c943a6d 07 Feb 2017 none — — Details →
v0.0.0-20160609040536-01cd508c173b 09 Jun 2016 none — — Details →
v0.0.0-20160526200558-86559cf7ca16 26 May 2016 none — — Details →
v0.0.0-20160525095813-f983201d5e04 25 May 2016 none — — Details →
v0.0.0-20160217194551-013a542e2791 17 Feb 2016 none — — Details →
v0.0.0-20160212230137-48d77b7b9c1d 12 Feb 2016 none — — Details →
v0.0.0-20150907173328-3ab20a7c61ef 07 Sep 2015 none — — Details →

All 38 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/moby/ipvs

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/moby/ipvs

Is github.com/moby/ipvs safe to use?

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

Vulert scores github.com/moby/ipvs 58/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/moby/ipvs affected?

No. v1.1.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/moby/ipvs should I use?

v1.1.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/moby/ipvs have?

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

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

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