Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7

Babylon vulnerable to chain half when transaction has fees different than ubbn

GHSA-56j4-446m-qrf6

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/babylonlabs-io/babylon/v2

    Affected
    < 2.2.0
    Fixed in
    2.2.0

  • Go github.com/babylonlabs-io/babylon

    Affected
    <= 1.1.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary Sending transactions with fees different than native Babylon genesis denom (ubbn) leads to chain halt. Impact Denial of Service - Due to panic in the x/distribution module BeginBlocker triggered by a error when sending fees from feeCollector to x/distribution module - https://github.com/cosmos/cosmos-sdk/blob/main/x/distribution/keeper/allocation.go#L28 Babylon Genesis will halt

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-56j4-446m-qrf6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-56j4-446m-qrf6

Advisory: Babylon vulnerable to chain half when transaction has fees different than `ubbn`
IDs: GHSA-56j4-446m-qrf6
Record: https://patchnext.com/advisories/ghsa-56j4-446m-qrf6 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/babylonlabs-io/babylon/v2 2.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/babylonlabs-io/babylon/v2: affected < 2.2.0; fixed in 2.2.0
- Go github.com/babylonlabs-io/babylon: affected <= 1.1.0

## Suggested inspection (read-only)
- Go github.com/babylonlabs-io/babylon/v2: check the installed version with your package manager.
- Go github.com/babylonlabs-io/babylon: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/babylonlabs-io/babylon/v2, github.com/babylonlabs-io/babylon.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-56j4-446m-qrf6 (GitHub-reviewed advisory GHSA-56j4-446m-qrf6 lists affected ranges: Go github.com/babylonlabs-io/babylon/v2 >=0 =0 <=1.1.0)

Commands are suggestions: review each one before running it.

Loading voting…