GHSA-q3jf-wmp2-47pg json
STARTTLS response injection allows a man-in-the-middle to forge SMTP replies
published yesterday modified yesterday also RUSTSEC-2026-0560
- cvss
- 4.8
- version 3.1, OSV
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
A man-in-the-middle can append replies of their own to the cleartext reply to `STARTTLS`. The client takes them for the server's replies to the commands it then sends over TLS, so the attacker can, for example, make a message that the server rejected look accepted.
Only connections upgraded with `STARTTLS` are affected (`Tls::Required` and `Tls::Opportunistic`, as set up by `starttls_relay`). Implicit TLS (`Tls::Wrapper`, as set up by `relay`) is not.
Patch / fix
Is GHSA-q3jf-wmp2-47pg 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| OSV | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected 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.