Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Nervos CKB BlockTimeTooNew should not be considered as invalid block

GHSA-r9rv-9mh8-pxf4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ckb 0.33.1), 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.33.0
    Fixed in
    0.33.1

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 Currently, when a node receives a block in future according to its local wall clock, it will mark the block as invalid and ban the peer. If the header's timestamp is more than 15 seconds ahead of our current time. In that case, the header may become valid in the future, and we don't want to disconnect a peer merely for serving us one too-far-ahead block header, to prevent an attacker from splitting the network by mining a block right at the 15 seconds boundary. Patches Upgrade to v0.33.1 or above. Workarounds Don't ban peer serving too-far-ahead block header.

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

    Published from ghsa record GHSA-r9rv-9mh8-pxf4

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-r9rv-9mh8-pxf4

Advisory: Nervos CKB BlockTimeTooNew should not be considered as invalid block
IDs: GHSA-r9rv-9mh8-pxf4
Record: https://patchnext.com/advisories/ghsa-r9rv-9mh8-pxf4 (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.33.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io ckb: affected <= 0.33.0; fixed in 0.33.1

## 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-r9rv-9mh8-pxf4 (GitHub-reviewed advisory GHSA-r9rv-9mh8-pxf4 lists affected ranges: crates.io ckb >=0 <=0.33.0)

Commands are suggestions: review each one before running it.

Loading voting…