- Exploited
- No known exploitation
- Fix
- Fixed in 0.11.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.11.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Versions of the vodozemac cryptography library (0.11.0 and 0.11.1) can leave encryption secrets lingering in memory longer than necessary and create extra copies of them, which slightly raises the risk of sensitive data being exposed. The attacker-facing access path is not specified, and no exploit code or active attacks are reported.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Versions 0.11.0 and 0.11.1 of vodozemac have degraded secret zeroization capabilities, due to changes in third-party cryptographic dependencies (chacha-20poly1305, sha2, hmac), which moved secret zeroization capabilities behind a feature flag while vodozemac disabled the default feature set.
Impact
The degraded zeroization capabilities could result in the production of more memory copies of encryption secrets and secrets could linger in memory longer than necessary. This marginally increases the risk of sensitive data exposure.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects crates.io packages
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.11.2.
Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
- vodozemaccrates.io
From 0.11.0 · fixed in 0.11.2
Evidence 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about RUSTSEC-2026-0445
Is RUSTSEC-2026-0445 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by RUSTSEC-2026-0445?
vodozemac (crates.io): from 0.11.0 before 0.11.2.Source: cve.now feed data
How do I fix RUSTSEC-2026-0445?
Upgrade to a fixed version: 0.11.2.Source: cve.now feed data