Skip to content
Fencer Intel
no cvss —

GHSA-45pr-7vv7-f64m json

Sending custom to-device messages may panics

published last mo. modified last mo. also RUSTSEC-2026-0318

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

Using the `IdentityBasedStrategy` setting when calling `Device::encrypt_event_raw` or `OlmMachine::encrypt_content_for_devices` may cause a panic if the recipient does not have cross-signing keys.

Patch / fix

  • crates.io matrix-sdk-crypto 0.19.0

Is GHSA-45pr-7vv7-f64m 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 matrix-sdk-crypto
>=0.0.0-0, <0.19.0
0.19.0

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.