VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/loxilb-io/loxilb: vulnerability history, versions and safety

github.com/loxilb-io/loxilb is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 74 releases, first recorded in Mar 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/loxilb-io/loxilb vulnerabilities

Vulert verdict on github.com/loxilb-io/loxilb v0.9.8 i

Updated on 23 Oct 2026

Careful: v0.9.8 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.9.8 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 25 Mar 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 1,885 i
  • Last release 20 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/loxilb-io/loxilb, 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-20261013074649-4fa515f08017 13 Oct 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20261013074649-4fa515f08017 13 Oct 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260911115143-98487453eaf1 11 Sep 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260812055929-3058f6b84b40 12 Aug 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260807050022-1201600d4f17 07 Aug 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260805061525-715403220dbd 05 Aug 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260723072739-c84bae4fbd58 23 Jul 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260619082433-a0f578c20af7 19 Jun 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20260327070520-2d74744861e5 27 Mar 2026 U1 Apache-2.0 No Details →
v0.9.9-0.20251215125323-893bcc282d61 15 Dec 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20251009115829-0a2c1931369a 09 Oct 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20250821053522-b8e9c55f5b0d 21 Aug 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20250625034635-2fa85113f453 25 Jun 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20250618080002-10fddc0296c9 18 Jun 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20250228135107-9e3e7c838840 28 Feb 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20250228032201-5c935da4cdd3 28 Feb 2025 U1 Apache-2.0 No Details →
v0.9.9-0.20250213100918-cfee8240aa3d 13 Feb 2025 U1 Apache-2.0 No Details →
v0.9.8 27 Jan 2025 U1 Apache-2.0 No Details →
v0.0.0-20241112025405-d80533fda889 12 Nov 2024 U1 Apache-2.0 No Details →
v0.9.8-0.20241112025405-d80533fda889 12 Nov 2024 U1 Apache-2.0 No Details →
v0.9.8-0.20241030004951-70c71611622a 30 Oct 2024 U1 Apache-2.0 No Details →
v0.9.7 25 Oct 2024 U1 Apache-2.0 No Details →
v0.9.7-0.20240813010205-dc7047dec261 13 Aug 2024 U1 Apache-2.0 No Details →
v0.9.6 05 Aug 2024 U1 Apache-2.0 No Details →
v0.9.6-0.20240719061309-8acf75a24625 19 Jul 2024 U1 Apache-2.0 No Details →
v0.9.5 15 Jul 2024 U1 Apache-2.0 No Details →
v0.9.5-0.20240612042241-691818497099 12 Jun 2024 U1 Apache-2.0 No Details →
v0.9.4 08 Jun 2024 U1 Apache-2.0 No Details →
v0.9.3 26 Apr 2024 U1 Apache-2.0 No Details →
v0.9.3-0.20240423134535-eadc7c918aa9 23 Apr 2024 U1 Apache-2.0 No Details →
v0.9.2 18 Apr 2024 U1 Apache-2.0 No Details →
v0.9.2-0.20240222122410-cf27dcbba728 22 Feb 2024 U1 Apache-2.0 No Details →
v0.9.2-0.20240220085805-45a3c0fe5504 20 Feb 2024 U1 Apache-2.0 No Details →
v0.9.2-0.20240210044727-0c643a1a4929 10 Feb 2024 U1 Apache-2.0 No Details →
v0.9.2-0.20240209024012-0d02bb413056 09 Feb 2024 U1 Apache-2.0 No Details →
v0.9.1 06 Feb 2024 U1 Apache-2.0 No Details →
v0.9.1-0.20231113232752-8ea1f0e075b9 13 Nov 2023 U1 Apache-2.0 No Details →
v0.9.0 13 Nov 2023 U1 Apache-2.0 No Details →
v0.8.9-0.20230810024402-d06a10a3a143 10 Aug 2023 U1 Apache-2.0 No Details →
v0.8.9-0.20230726023408-f0438f8214df 26 Jul 2023 U1 Apache-2.0 No Details →
v0.8.9-0.20230721143052-fef2d6182ac1 21 Jul 2023 U1 Apache-2.0 No Details →
v0.8.9-0.20230714131918-46a29ab22bce 14 Jul 2023 U1 Apache-2.0 No Details →
v0.8.9-0.20230628070411-423f238f39dd 28 Jun 2023 U1 Apache-2.0 No Details →
v0.8.8 28 Jun 2023 U1 Apache-2.0 No Details →
v0.8.8-0.20230613073103-0a31903170f8 13 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7 13 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609153030-518dec148742 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609072305-28cf5db4ebff 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609061356-65b69d0280a2 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609050658-3e84a9be63a0 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609030317-20463d25c4c4 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609010812-004f641a43ae 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230609002034-e1345cd69ca6 09 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230608154102-30c4c70b3031 08 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230608145116-d0a5b7b433cc 08 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230608082344-ab93f3dcfb9b 08 Jun 2023 U1 Apache-2.0 No Details →
v0.8.7-0.20230608060709-cab26b4767e7 08 Jun 2023 U1 Apache-2.0 No Details →
v0.8.6 22 May 2023 U1 Apache-2.0 No Details →
v0.8.5 15 May 2023 U1 Apache-2.0 No Details →
v0.8.5-0.20230424171508-042ba71ebbfd 24 Apr 2023 U1 Apache-2.0 No Details →
v0.8.4 19 Apr 2023 U1 Apache-2.0 No Details →
v0.8.4-0.20230215142113-0e8816316ae8 15 Feb 2023 U1 Apache-2.0 No Details →
v0.8.3 10 Feb 2023 U1 Apache-2.0 No Details →
v0.8.3-0.20230208075101-10eca96c47bd 08 Feb 2023 U1 Apache-2.0 No Details →
v0.8.2 02 Feb 2023 U1 Apache-2.0 No Details →
v0.8.1 01 Feb 2023 U1 Apache-2.0 No Details →
v0.8.0 30 Jan 2023 U1 Apache-2.0 No Details →
v0.7.1-0.20230106113835-9ccdb99e9817 06 Jan 2023 U1 Apache-2.0 No Details →
v0.7.1-0.20230105125540-853509a419df 05 Jan 2023 U1 Apache-2.0 No Details →
v0.7.1-0.20221115011926-a79722fd2bcb 15 Nov 2022 U1 Apache-2.0 No Details →
v0.7.1-0.20221004054043-45db9ac210f9 04 Oct 2022 U1 Apache-2.0 No Details →
v0.7.0 07 Sep 2022 U1 Apache-2.0 No Details →
v0.7.0-beta.0.20220827014119-fb78540ddab1 27 Aug 2022 U1 Apache-2.0 No Details →
v0.7.0-beta 27 Aug 2022 U1 Apache-2.0 No Details →

All 74 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/loxilb-io/loxilb

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-53348: Vulnerability in github.com/loxilb-io/loxilb - Potential Security Risk N/A unrated No fix published 25 Mar 2025

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/loxilb-io/loxilb

Is github.com/loxilb-io/loxilb safe to use?

Vulert records 1 vulnerabilities for github.com/loxilb-io/loxilb in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/loxilb-io/loxilb's Vulert package health score?

Vulert scores github.com/loxilb-io/loxilb 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/loxilb-io/loxilb affected?

Yes. v0.9.8, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/loxilb-io/loxilb should I use?

v0.9.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/loxilb-io/loxilb have?

1 vulnerability is recorded for github.com/loxilb-io/loxilb in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/loxilb-io/loxilb vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/loxilb-io/loxilb in the last 12 months, and the oldest entry in this database dates to 25 Mar 2025. 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/loxilb-io/loxilb 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/loxilb-io/loxilb for upcoming vulnerabilities?

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