GHSA-pmvc-x69f-5p9f json
Unbounded buffering of an SMTP reply allows a malicious server to exhaust memory
published yesterday modified yesterday also RUSTSEC-2026-0565
- 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
A malicious or compromised server can send a reply line that never ends, which the client buffers until memory runs out. A reply made of many short lines also keeps a CPU core busy: for a few seconds per reply since 0.11.22, for as long as the server wants before it.
Applications that connect only to a trusted server over implicit TLS are not exposed; the risk applies to clients that may connect to untrusted servers, or that use `STARTTLS` or no TLS, where a man-in-the-middle can forge the reply.
Patch / fix
Is GHSA-pmvc-x69f-5p9f 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.