Arbitrary Code Injection Affecting aiosmtplib package, versions <5.1.2-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.26% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN14-AIOSMTPLIB-19166041
  • published22 Aug 2026
  • disclosed20 Aug 2026

Introduced: 20 Aug 2026

NewCVE-2026-55558  (opens in a new tab)
CWE-74  (opens in a new tab)

How to fix?

Upgrade Debian:14 aiosmtplib to version 5.1.2-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream aiosmtplib package and not the aiosmtplib package as distributed by Debian. See How to fix? for Debian:14 relevant fixed versions and status.

aiosmtplib is an asynchronous SMTP client for use with asyncio. Prior to 5.1.2, SMTPProtocol.start_tls in src/aiosmtplib/protocol.py consumes the server's 220 response and starts the TLS handshake without clearing SMTPProtocol._buffer. An active network attacker can place attacker-chosen SMTP response lines after the plaintext 220 response in the same network segment. The method then calls loop.start_tls; those bytes survive the transport upgrade and are parsed as the first response from inside the TLS session, desynchronizing subsequent SMTP command and response pairs. Connections using start_tls=True or opportunistic STARTTLS are affected, while connections using use_tls=True are not. This issue is fixed in version 5.1.2.