Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The dcrypt-api crate, versions before 2.0.0, has safe ErrorRegistry operations that can cause undefined behavior when the default std feature is enabled. Ordinary safe Rust code calling the registry can trigger mismatched deallocation, type confusion, and use-after-free, and crates that re-export this API are affected too. Upgrade to dcrypt-api 2.0.0 or later; the source says there is no reliable workaround while using the affected registry API.
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-7hc7-h3f2-r4j6
- OSV: GHSA-7hc7-h3f2-r4j6
- crates.io/crates/dcrypt-api
- rustsec.org/advisories/RUSTSEC-2026-0242.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