VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/babylonlabs-io/babylon/v4: vulnerability history, versions and safety

github.com/babylonlabs-io/babylon/v4 is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 92 releases, from Nov 2025 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 09 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/babylonlabs-io/babylon/v4 vulnerabilities

Vulert verdict on github.com/babylonlabs-io/babylon/v4 v4.6.0 i

Updated on 23 Oct 2026

Action needed: v4.6.0 has 4 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 72/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v4.6.0 — affected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 09 Dec 2025 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Stars 103 i
  • Last release this month i
  • Licence non-standard 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/babylonlabs-io/babylon/v4, 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
v4.6.0 22 Oct 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20261002061542-c2f731f4531b 02 Oct 2026 H2 M2 — Yes Details →
v4.5.0 29 Sep 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260928181603-e750524b3780 28 Sep 2026 H2 M2 — Yes Details →
v4.4.0 06 Aug 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260804131933-0de36afadb84 04 Aug 2026 H2 M2 — Yes Details →
v4.3.1 21 Jul 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260701204319-a3b6540f3d79 01 Jul 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260527160023-fe3dd3e8c59a 27 May 2026 H2 M2 — Yes Details →
v4.3.1-0.20260505113955-cc357f09f2fb 05 May 2026 H2 M2 — Yes Details →
v4.3.0 05 May 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260430154957-d96cd9de2ead 30 Apr 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260415170036-3e80c713d814 15 Apr 2026 H2 M2 — Yes Details →
v4.2.7 14 Apr 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260414054837-d8618f1684af 14 Apr 2026 H2 M2 — Yes Details →
v4.2.6 13 Apr 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260316204038-65d793a0a8b8 16 Mar 2026 H2 M2 — Yes Details →
v4.2.5 04 Feb 2026 H2 M2 — Yes Details →
v4.2.2-0.20260203174927-e4ae3db41721 03 Feb 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260203151228-bc2f07d74e52 03 Feb 2026 H2 M2 — Yes Details →
v4.2.4 29 Jan 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260127150928-7b3fcdfb5039 27 Jan 2026 H2 M2 — Yes Details →
v4.2.3 09 Jan 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260109043052-9a510829ae95 09 Jan 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20260105171242-c5e5a5b33d87 05 Jan 2026 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251218114411-e14b24bbd6f0 18 Dec 2025 H2 M2 — Yes Details →
v4.2.2 16 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251216170335-02aa29502375 16 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251211142756-74a4db8327a1 11 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251211024100-bb99ec280d49 11 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251209163031-41a4b20bbb64 09 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251208195159-eee5803a1312 08 Dec 2025 H2 M2 — Yes Details →
v4.2.1 08 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251208120919-e4f1317c19e1 08 Dec 2025 H2 M2 — Yes Details →
v4.2.0 04 Dec 2025 H2 M2 — Yes Details →
v4.1.1-0.20251204083749-f79ad58c1d5b 04 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251204082108-b833baeda1b4 04 Dec 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251201140620-7989574892c2 01 Dec 2025 H2 M2 — Yes Details →
v4.1.1-0.20251126171733-0b17a7f2dbf1 26 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251125123555-292b5d496277 25 Nov 2025 H2 M2 — Yes Details →
v4.1.0 24 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251124073632-953724e594f9 24 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251118185813-be16eb0528cc 18 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251117013457-c8ef72fa5bc7 17 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251113114053-7ae4709949b1 13 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251113074244-0b779d72ddd9 13 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251113015205-bcb6c58937f4 13 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251111141225-13f784296bd8 11 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251111135851-b06e47e182a6 11 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251111133356-30a0472844bc 11 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251110033423-1d437f04f170 10 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251107112138-9aa29e318b46 07 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251107091300-2e0fe7188a02 07 Nov 2025 H2 M2 — Yes Details →
v4.0.0 06 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251106192908-02043b17701e 06 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251105223733-a143cb133083 05 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251105221927-a3823fdafd2f 05 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251105214545-09ff66b340e9 05 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251105173336-6a60bb1f7da6 05 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251105104712-e39a875af2a7 05 Nov 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251105050521-487ddc7952c5 05 Nov 2025 H2 M2 — Yes Details →
v4.0.0-rc.3 31 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251031084733-39d98894403d 31 Oct 2025 H2 M2 — Yes Details →
v4.0.0-rc.2 30 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251029161113-90220756ed77 29 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251029041923-54247ad2b7b8 29 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251027183029-38465a43ff50 27 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251026143957-baa327f96783 26 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251020130746-18f69ed1dddb 20 Oct 2025 H2 M2 — Yes Details →
v4.0.0-rc.1 17 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251015193522-b8dd48ecac34 15 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20251001210615-f23219536b99 01 Oct 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925.0.20250926094400-f6d409847a43 26 Sep 2025 H2 M2 — Yes Details →
v4.0.0-rc.0 26 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250924171224-0a9cfa63316a 24 Sep 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250925 24 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250924134411-d92761c28530 24 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250923192108-be5f6fbb937d 23 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250923184422-21dc57bf8b6d 23 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250923142016-3cb49f44f954 23 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250923100136-ff6ae3d7302c 23 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250923061816-8867bd62df99 23 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250905061855-669c7287572b 05 Sep 2025 H2 M2 — Yes Details →
v4.0.0-20250609140208-52355fa83078 09 Jun 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250522.0.20250608144918-51359793bc94 08 Jun 2025 H2 M2 — Yes Details →
v4.0.0-20250607161008-d4e234502e20 07 Jun 2025 H2 M2 — Yes Details →
v4.0.0-20250604163302-bf39dc183500 04 Jun 2025 H2 M2 — Yes Details →
v4.0.0-20250604124631-df8efed11cfd 04 Jun 2025 H2 M2 — Yes Details →
v4.0.0-20250601202610-a2869bd21464 01 Jun 2025 H2 M2 — Yes Details →
v4.0.0-20250526154746-5f7c227d0136 26 May 2025 H2 M2 — Yes Details →
v4.0.0-20250526141811-da416c669e72 26 May 2025 H2 M2 — Yes Details →
v4.0.0-snapshot.250522 22 May 2025 H2 M2 — Yes Details →

All 92 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 4

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/babylonlabs-io/babylon/v4

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Panic Vulnerability in Babylon Package Due to Nil BlockHash in BLS Vote Extensions 8.7 high 4.2.0 08 Dec 2025
Chain Halt Vulnerability in Babylon Package Due to Malformed Vote Extensions 7.0 high 4.1.0 24 Nov 2025
BIP322 Signature Compliance Issue in Babylon Package 6.9 medium 4.1.0 24 Nov 2025
Phantom Stake Vulnerability in Babylon Costaking Package 6.9 medium 4.2.0 09 Dec 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/babylonlabs-io/babylon/v4

Is github.com/babylonlabs-io/babylon/v4 safe to use?

Vulert records 4 vulnerabilities for github.com/babylonlabs-io/babylon/v4 in Go: 0 critical, 2 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/babylonlabs-io/babylon/v4's Vulert package health score?

Vulert scores github.com/babylonlabs-io/babylon/v4 72/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/babylonlabs-io/babylon/v4 affected?

Yes. v4.6.0, the version you would install today, has 4 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does github.com/babylonlabs-io/babylon/v4 have?

4 vulnerabilities are recorded for github.com/babylonlabs-io/babylon/v4 in the Go ecosystem: 0 critical, 2 high, 2 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/babylonlabs-io/babylon/v4 vulnerabilities disclosed?

4 vulnerabilities were recorded for github.com/babylonlabs-io/babylon/v4 in the last 12 months, and the oldest entry in this database dates to 24 Nov 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/babylonlabs-io/babylon/v4 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/babylonlabs-io/babylon/v4 for upcoming vulnerabilities?

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