RUSTSEC-2026-0561 json
Missing dot-stuffing after a bare LF or CR allows SMTP command injection
published yesterday modified yesterday
- 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
Someone who controls the content of a message with bare LF or CR line endings can end it early with `\n.\n` on a server that takes a bare LF for a line ending. What follows is read by the server as SMTP commands, which can be used to send other messages over the same authenticated connection.
This affects messages passed to `send_raw`, and message bodies that are sent without being encoded. The LF line endings of a `String` body are converted to CRLF before it is sent.
Patch / fix
Is RUSTSEC-2026-0561 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | lettre | >=0.0.0-0, <0.11.24 |
0.11.24 |
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.