Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Nervos CKB Snappy decompress length can be very large and causes out of memory error

GHSA-3gjh-29fv-8hr6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ckb 0.34.2), redeploy, then verify what is actually installed.

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

  • crates.io ckb

    Affected
    <= 0.34.1
    Fixed in
    0.34.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact Adversary can create message which compressed size is less than the package limit but the decompressed length is very large such as 1G. It will cost the node many memories to process the network messages, and on the system with less than 1G memory, the process is killed directly because of out of memory error. Patches The node must check the decompress length before allocating the memory for the message. References https://github.com/nervosnetwork/ckb/blob/687d797f1888dd05d1f38ce6d1bef3e5b9b6e38b/network/src/compress.rs#L68 https://github.com/BurntSushi/rust-snappy/blob/master/src/decompress.rs#L106 https://github.com/BurntSushi/rust-snappy/blob/6cfb836463b9b3ac48ca7cd15d0a50d030e95769/src/decompress.rs#L30

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

    Published from ghsa record GHSA-3gjh-29fv-8hr6

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-3gjh-29fv-8hr6

Advisory: Nervos CKB Snappy decompress length can be very large and causes out of memory error
IDs: GHSA-3gjh-29fv-8hr6
Record: https://patchnext.com/advisories/ghsa-3gjh-29fv-8hr6 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ckb 0.34.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io ckb: affected <= 0.34.1; fixed in 0.34.2

## Suggested inspection (read-only)
- crates.io ckb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ckb.
- 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-3gjh-29fv-8hr6 (GitHub-reviewed advisory GHSA-3gjh-29fv-8hr6 lists affected ranges: crates.io ckb >=0 <=0.34.1)

Commands are suggestions: review each one before running it.

Loading voting…