Advisory record · GHSA-7hc7-h3f2-r4j6

Safe ErrorRegistry APIs can cause undefined behavior

No CVSS score

Published by the GitHub Advisory Database at 9 Aug 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
dcrypt-apicrates.io>=0.0.0-0, <2.0.02.0.0
Identifiers
GHSA-7hc7-h3f2-r4j6 · RUSTSEC-2026-0242
Published
9 Aug 2026
Updated
12 Oct 2026

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.

Written 3 Nov 2026.

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

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.