cargo package report

Is secp256k1 safe?

1 known vulnerability, worst severity MODERATE.

cvss

5.0

how bad it is if exploited, out of 10

epss

not scored

chance of exploitation in the next 30 days

xyz score

not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-969w-q74q-9j8v, the advisory selected below

// advisories

GHSA-969w-q74q-9j8v

MODERATE

Because of incorrect bounds on method Secp256k1::preallocatedgennew it was possible to cause use-after-free from safe consumer code. It was also possible to "free" memory not allocated by the appropriate allocator.

Affected: >= 0.24.0, < 0.24.2, >= 0.23.0, < 0.23.5, >= 0.14.0, < 0.22.2
Fixed in: 0.24.2
Published: 2022-12-08
Source: github

GHSA reference reference

// dependencies

0 direct

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

Checked 2026-09-22 at 01:46 UTC. The most recent advisory here was published 2022-12-08. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Is secp256k1 safe? cargo package security report | CyberXYZ