- 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
The Olm root key ratchet in vodozemac does not zeroize its HKDF output after use, leaving copies of root and chain keys in freed heap memory, so an attacker who can read the process's memory (for example through a separate memory-disclosure bug, a core dump, or swapped-out pages) could recover keys from earlier ratchet steps. A recovered chain key lets them decrypt messages in that chain, weakening Olm's forward secrecy for affected sessions.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In version 0.11.1 and earlier of vodozemac, the Olm root key ratchet did not zeroize its HKDF output after use. Each ratchet step left a copy of the new root key and chain key in freed heap memory.
Impact
An attacker who can read the process's memory, for example through a separate memory-disclosure bug, a core dump, or swapped-out pages, may recover root keys and chain keys from earlier ratchet steps. A leaked chain key allows decrypting the messages in that chain, weakening Olm's forward secrecy for affected sessions.
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.0.0-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-0451
Is RUSTSEC-2026-0451 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-0451?
vodozemac (crates.io): from 0.0.0-0 before 0.11.2.Source: cve.now feed data
How do I fix RUSTSEC-2026-0451?
Upgrade to a fixed version: 0.11.2.Source: cve.now feed data