Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The starkbank-ecdsa NuGet package is vulnerable in versions before 1.3.2. Its verify function does not check that the signature is non-zero, so an attacker can forge signatures on arbitrary messages. The source does not say what access an attacker needs. Upgrade to version 1.3.2, which fixes the issue.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.011, the 64th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:24 UTC First seen by agentprime
- 31 Oct 2026, 15:24 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-j3jw-j2j8-2wv9
- OSV: GHSA-j3jw-j2j8-2wv9
- nvd.nist.gov/vuln/detail/CVE-2021-43569
- github.com/starkbank/ecdsa-dotnet
- github.com/starkbank/ecdsa-dotnet/releases/tag/v1.3.2
- research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries