VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

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

i
2 vulnerabilities recorded H2
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/babylonlabs-io/babylon/v2 vulnerabilities

Vulert verdict on github.com/babylonlabs-io/babylon/v2 v2.3.2 i

Updated on 23 Oct 2026

Action needed: v2.3.2 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 79/100
  • Security No known security issues
  • 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 v2.3.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 08 Jul 2025 i
  • Highest CVSS 8.9 i
  • With no published fix 0 i
  • Stars 103 i
  • Last release 12 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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/v2, 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
v2.3.2 15 Oct 2025 H1 — Yes Details →
v2.3.1 09 Oct 2025 H1 — Yes Details →
v2.3.0 16 Sep 2025 H1 — Yes Details →
v2.3.0-snapshot.290825 27 Aug 2025 H1 — Yes Details →
v2.2.0 28 Jun 2025 H1 — Yes Details →
v2.1.0 19 Jun 2025 H1 — Yes Details →
v2.0.0 12 Jun 2025 H1 — Yes Details →
v2.0.0-rc.4 10 Jun 2025 H1 — Yes Details →
v2.0.0-rc.3 07 Jun 2025 H1 — Yes Details →
v2.0.0-rc.2 03 Jun 2025 H1 — Yes Details →
v2.0.0-rc.1 30 May 2025 H1 — Yes Details →
v2.0.0-20250516132716-b161e0d8c06a 16 May 2025 H1 — Yes Details →
v2.0.0-rc.0 16 May 2025 H1 — Yes Details →
v2.0.0-20250516070223-95301c8c1cde 16 May 2025 H1 — Yes Details →
v2.0.0-20250515213425-a1f0989a43f1 15 May 2025 H1 — Yes Details →
v2.0.0-20250515182059-50dcbcb1bd7b 15 May 2025 H1 — Yes Details →
v2.0.0-20250515180246-cfefa7e0206e 15 May 2025 H1 — Yes Details →
v2.0.0-20250515025337-7fcb2f3c570b 15 May 2025 H1 — Yes Details →
v2.0.0-20250514134626-7be6dbe5979f 14 May 2025 H1 — Yes Details →
v2.0.0-20250514123547-9635953bada2 14 May 2025 H1 — Yes Details →
v2.0.0-20250514094232-710774df68c8 14 May 2025 H1 — Yes Details →
v2.0.0-20250514092856-e7e0e1d6123a 14 May 2025 H1 — Yes Details →
v2.0.0-20250513054822-500e47649c45 13 May 2025 H1 — Yes Details →
v2.0.0-20250512132247-e32855f8819f 12 May 2025 H1 — Yes Details →
v2.0.0-20250512085309-17c7ca2f8715 12 May 2025 H1 — Yes Details →
v2.0.0-20250509085711-6219ca9b4e60 09 May 2025 H1 — Yes Details →
v2.0.0-20250508132829-4ca8f9303802 08 May 2025 H1 — Yes Details →
v2.0.0-20250508054025-8e5ba126eec2 08 May 2025 H1 — Yes Details →
v2.0.0-20250507134425-aa717c1cad58 07 May 2025 H1 — Yes Details →
v2.0.0-20250505130249-7d5a8c83c48a 05 May 2025 H1 — Yes Details →
v2.0.0-20250505064752-da0a8b7ceda3 05 May 2025 H1 — Yes Details →
v2.0.0-20250505060702-2307080b5541 05 May 2025 H1 — Yes Details →
v2.0.0-20250502144617-eab0f83302ff 02 May 2025 H1 — Yes Details →
v2.0.0-20250501173201-0e0ebdb796a9 01 May 2025 H1 — Yes Details →
v2.0.0-20250501114157-01b7cb6c1c56 01 May 2025 H1 — Yes Details →
v2.0.0-20250501064105-db20d092d8fd 01 May 2025 H1 — Yes Details →
v2.0.0-20250430154805-3dfc48e1d987 30 Apr 2025 H1 — Yes Details →
v2.0.0-20250429094530-d204f9535d6d 29 Apr 2025 H1 — Yes Details →
v2.0.0-20250428172337-7c59da5ee252 28 Apr 2025 H1 — Yes Details →
v2.0.0-20250428154453-92b7d459aa64 28 Apr 2025 H1 — Yes Details →

All 40 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 2

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

03 Vulnerabilities

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

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in Babylon Package v2 - Chain Halt at Epoch Boundary 8.9 high 2.1.0 08 Jul 2025
Chain Halt Vulnerability in Babylon Package Due to Non-Native Transaction Fees 8.7 high 2.2.0 30 Jun 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/v2

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

Vulert records 2 vulnerabilities for github.com/babylonlabs-io/babylon/v2 in Go: 0 critical, 2 high, 0 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/v2's Vulert package health score?

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

Yes. v2.3.2, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/babylonlabs-io/babylon/v2 should I use?

v2.3.2 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/babylonlabs-io/babylon/v2 have?

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

0 vulnerabilities were recorded for github.com/babylonlabs-io/babylon/v2 in the last 12 months, and the oldest entry in this database dates to 30 Jun 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/v2 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/v2 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/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.