Secure gate: `Fixed` and `Dynamic` secret wrappers were not zeroized on drop
Affects secure-gateSource GCVE Database
Rated High by Threat Radar's AI analysis
- Patch
- Available – fixed in 0.8.0-rc.1
Data as of 22 Nov 2026, 10:39 UTC
What to do
Upgrade secure-gate to 0.8.0-rc.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iosecure-gatepkg:cargo/secure-gateOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to secure-gate version 0.8.0-rc.1 or later, where the zeroization on drop is properly implemented. All affected versions have been yanked from crates.io, so avoid using versions >=0.5.0 and <0.8.0-rc.1. No other mitigation is necessary as the fix is available and official.
Description
The secure-gate library versions from 0.5.0 up to but not including 0.8.0-rc.1 contain a vulnerability where the Fixed<T> and Dynamic<T> secret wrappers do not zeroize (wipe) their contents upon being dropped. This means secret data may remain in memory after the wrapper goes out of scope, potentially exposing sensitive information through memory disclosure such as core dumps or swap files. The issue was fixed starting with version 0.8.0-rc.1 by adding proper zeroization on drop and making zeroize a required dependency.