Skip to content
Fencer Intel
no cvss —

GHSA-pqp6-f7wc-6498 json

Panic when decoding malformed Ed25519 keys from Base64

published 3d ago modified 2d ago also RUSTSEC-2026-0510

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

In version 0.11.1 and earlier of vodozemac, Ed25519PublicKey::from_base64() and Ed25519SecretKey::from_base64() panic on malformed input instead of returning an error, if the input decodes to 31 or 33 bytes instead of the expected 32 bytes. An attacker who can supply a key to an application using vodozemac can crash it.

## Impact

Ed25519 public keys are routinely received from other Matrix users and servers, so a malicious party can publish a crafted key that crashes clients parsing it.

The impact is limited to denial of service; no key disclosure or signature forgery is possible.

Patch / fix

  • crates.io vodozemac 0.11.2

Is GHSA-pqp6-f7wc-6498 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io vodozemac
>=0.0.0-0, <0.11.2
0.11.2

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.