Live › vulnerability › CVE-2026-87864
Go to dashboardWhen the CURLOPT_CRLF option is enabled, curl reports the wrong byte count for IMAP APPEND literals, so the extra bytes are read by the server as new IMAP commands. An attacker who can control the uploaded message content can run commands inside the authenticated IMAP session.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only programs that use libcurl with CURLOPT_CRLF set while uploading to IMAP servers with APPEND are exposed. Applications that never upload to IMAP or never enable CRLF conversion can skip it. The sources do not name affected curl versions.
No product ranges from the sources yet.
CURLOPT_CRLF or --crlf usage with IMAP uploads.curl --version.Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Enabling CURLOPT_CRLF causes curl to advertise the raw input byte count in
the IMAP APPEND {N} literal while transmitting line-ending expanded data.
The server reads only $N$ bytes for the payload, causing the remaining
overflow bytes to be interpreted and executed as pipelined IMAP commands
within the authenticated session.
This page as .md · .json · in your agent: get_signal("CVE-2026-87864")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.