NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
LOW severity

CVE-2024-58263 — cosmwasm-std

LOWFix: CosmWasm/cosmwasm@607e7fc

CVE-2024-58263 is a low-severity (CVSS 3.7) CWE-190 vulnerability in cosmwasm-std. A fix is available for cosmwasm-std — see the affected versions and patch details below.

CosmWasm affected by arithmetic overflows

Also known asRUSTSEC-2024-0338
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-58263.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk
0.00%0.33%0.66%1.00%0.1%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🦀cosmwasm-std🦀cosmwasm-std🦀cosmwasm-std

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

Some mathematical operations in cosmwasm-std use wrapping math instead of panicking on overflow for very big numbers. This can lead to wrong calculations in contracts that use these operations.

Affected functions:

  • Uint{256,512}::pow / Int{256,512}::pow
  • Int{256,512}::neg

Affected if overflow-checks = true is not set:

  • Uint{64,128}::pow / Int{64,128}::pow
  • Int{64,128}::neg

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iocosmwasm-std≥ 1.3.0&&< 1.4.41.4.4cargo update -p cosmwasm-std --precise 1.4.4
🦀crates.iocosmwasm-std≥ 1.5.0&&< 1.5.41.5.4cargo update -p cosmwasm-std --precise 1.5.4
🦀crates.iocosmwasm-std≥ 2.0.0&&< 2.0.22.0.2cargo update -p cosmwasm-std --precise 2.0.2

Affected Products

1 product · 3 configurations
Application
cosmwasm-stdcosmwasm
≥ 2.0.0 && < 2.0.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cosmwasm-std, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update cosmwasm-std to 1.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-58263 is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Some mathematical operations in `cosmwasm-std` use wrapping math instead of panicking on overflow for very big numbers. This can lead to wrong calculations in contracts that use these operations. Affected functions: - `Uint{256,512}::pow` / `Int{256,512}::pow` - `Int{256,512}::neg` Affected if `overflow-checks = true` is not set: - `Uint{64,128}::pow` / `Int{64,128}::pow` - `Int{64,128}::neg`
O3 Security · Impact-Aware SCA

Is CVE-2024-58263 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-58263: cosmwasm-std — Fixed in 1.4.4