Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The dcrypt-sign crate before 2.0.0 accepted the Edwards identity and other noncanonical or small-order values as Ed25519 public keys, so a signature with a chosen R and S = 1 could verify for any message. An attacker who can supply a public key to a consumer that trusts externally supplied dcrypt Ed25519 keys could forge authorizations. Upgrade to dcrypt-sign 2.0.0 or later, and audit registered keys and trust stores; the source does not recommend a wrapper around the affected verifier as a complete workaround.
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
No source has published a CVSS score for this record yet.
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-7j32-2mpw-c784
- OSV: GHSA-7j32-2mpw-c784
- crates.io/crates/dcrypt-sign
- rustsec.org/advisories/RUSTSEC-2026-0240.html
- github.com/ioi-foundation/dcrypt/commit/c99cc86f0ee353010cd202cbcd2c310371b0bbb8
- github.com/ioi-foundation/dcrypt/commit/c99cc86f0ee353010cd202cbcd2c310371b0bbb8
- github.com/ioi-foundation/dcrypt/releases/tag/v2.0.0