RUSTSEC-2026-0561: Missing dot-stuffing after a bare LF or CR allows SMTP command injection

Published Nov 17, 2026
·
Updated

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 sendraw, 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.

Affected Software

1 affected componentFixes available
rust/lettre>=0.0.0-0<0.11.24
0.11.24

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/lettre to a version that resolves this vulnerability.

    Fixed in 0.11.24

Event History

Nov 17, 2026
Advisory Published
via OSV·12:00 PM
Data Sourced
via OSV·12:00 PM
DescriptionAffected Software

Frequently Asked Questions

1

Which message inputs are affected?

The issue affects content passed to send_raw and message bodies sent without encoding. A String body is not affected by LF-only line endings because lettre converts those LF line endings to CRLF before sending.

2

What must an attacker control to exploit this?

An attacker must control message content containing bare LF or CR line endings and be able to include an end-of-data sequence such as \n.\n. Exploitation also depends on the SMTP server accepting a bare LF as a line ending.

3

What is the practical impact after successful exploitation?

The attacker can terminate the message data early and cause following content to be interpreted as SMTP commands. Those commands can be used to send additional messages over the same authenticated SMTP connection.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203