How severe is GHSA-49xc-52mp-cc9j?

GHSA-49xc-52mp-cc9j has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-49xc-52mp-cc9j?

GHSA-49xc-52mp-cc9j affects the following packages: nimiq-blockchain (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-49xc-52mp-cc9j?

No patched version of nimiq-blockchain has shipped for GHSA-49xc-52mp-cc9j yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-49xc-52mp-cc9j in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nimiq-blockchain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-49xc-52mp-cc9j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-49xc-52mp-cc9j?

O3 pinpoints whether GHSA-49xc-52mp-cc9j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-49xc-52mp-cc9j actively exploited in the wild?

No public exploit code has been indexed for GHSA-49xc-52mp-cc9j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-49xc-52mp-cc9j?

GHSA-49xc-52mp-cc9j is classified as CWE-1284 (CWE-1284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-49xc-52mp-cc9j published, and has it been updated?

GHSA-49xc-52mp-cc9j was published on April 10, 2026 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

CRITICAL severity

GHSA-49xc-52mp-cc9j

CRITICAL

GHSA-49xc-52mp-cc9j is a critical-severity (CVSS 9.1) CWE-1284 vulnerability in nimiq-blockchain. O3 Security confirms whether GHSA-49xc-52mp-cc9j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

nimiq-blockchain is missing a wall-clock upper bound on block timestamps

Also known asCVE-2026-40093

Published

Apr 10, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Apr 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀nimiq-blockchain

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Block timestamp validation enforces that timestamp >= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.

Patches

TBD

Workarounds

No know workarounds.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`nimiq-blockchain`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nimiq-blockchain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of nimiq-blockchain has shipped for GHSA-49xc-52mp-cc9j yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-49xc-52mp-cc9j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-49xc-52mp-cc9j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Block timestamp validation enforces that `timestamp >= parent.timestamp` for non-skip blocks and `timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT` for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via `Policy::supply_at()` and `batch_delay()` in `blockchain/src/reward.rs`, inflating the monetary supply beyond the intended emission schedule. ### Patches TBD ### Workarounds No know workarounds.

O3 Security · Impact-Aware SCA

Is GHSA-49xc-52mp-cc9j in your dependencies?

O3 detects GHSA-49xc-52mp-cc9j across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works