CVE-2026-115559
IMAP4.starttls() wraps the socket in TLS but leaves self._readbuf, imaplib's own read-ahead...
Impact
IMAP4.starttls() wraps the socket in TLS but leaves self._readbuf, imaplib's own read-ahead buffer, untouched. Any plaintext bytes that arrived in the same recv() as the tagged OK to STARTTLS are returned by readline() after the handshake, so the client treats them as the first responses on the protected channel. A network attacker who cannot break TLS can append forged lines after the server's OK, let the handshake complete with the real server and a valid certificate, and have the client accept the forged CAPABILITY and the forged tagged completion of the next command. This is the STARTTLS command/response injection class of CVE-2011-0411.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data or systems being changed.
Affected products · Python Software Foundation
| Product | Affected versions |
|---|---|
| CPython | before 3.16.0 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/python/cpython/pull/160370
- https://github.com/python/cpython/issues/160369
- https://mail.python.org/archives/list/security-announce@python.org/thread/LVAGFOFG26QVXEM6VXXPRMMOZBHM4CVB/
- https://nvd.nist.gov/vuln/detail/CVE-2026-115559
- https://github.com/advisories/GHSA-xmjp-7865-vg6q
- https://mail.python.org/archives/list/security-announce@python.org/thread/LVAGFOFG26QVXEM6VXXPRMMOZBHM4CVB