Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of starkbank-ecdsa below 1.0.1 are affected. The verify function does not check that the signature is non-zero, so an attacker can forge signatures on arbitrary messages without needing a valid key. Upgrade to starkbank-ecdsa 1.0.1 or later; no workaround is listed.
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.010, 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:11 UTC First seen by agentprime
- 31 Oct 2026, 15:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-r28h-x6hv-2fq3
- OSV: GHSA-r28h-x6hv-2fq3
- nvd.nist.gov/vuln/detail/CVE-2021-43570
- github.com/starkbank/ecdsa-java/pull/16
- github.com/starkbank/ecdsa-java/commit/ed22e484186d6c66d3686bfe39d01bdbabf219b6
- github.com/starkbank/ecdsa-java
- github.com/starkbank/ecdsa-java/releases/tag/v1.0.1
- research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries