Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-82973 Overview
CVE-2026-82973 is a CRLF injection vulnerability in the psyb0t/docker-mailbox project affecting versions prior to 0.4.13. The flaw resides in the IMAP command construction logic, where user-supplied folder, UID, and search values are concatenated into IMAP commands without neutralizing carriage return and line feed sequences. When bearer-token authentication is not configured, a remote unauthenticated attacker can inject additional IMAP commands into an authenticated upstream mailbox connection. The vulnerability is classified under CWE-93: Improper Neutralization of CRLF Sequences.
Critical Impact
Unauthenticated attackers can execute arbitrary IMAP commands against upstream mailboxes, exposing message contents, altering folder state, and disrupting mailbox availability.
Affected Products
- psyb0t/docker-mailbox versions prior to 0.4.13
- Deployments without bearer-token authentication configured
- Any downstream service exposing the docker-mailbox HTTP API to untrusted networks
Discovery Timeline
- 2026-09-29 - CVE CVE-2026-82973 published to NVD
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-82973
Vulnerability Analysis
The docker-mailbox service acts as an HTTP-to-IMAP bridge, translating REST-style requests into IMAP protocol commands issued over an authenticated upstream connection. Request parameters including folder names, message UIDs, and search criteria flow directly into IMAP command strings. Because the IMAP protocol uses CRLF (\r\n) as its command terminator, any unsanitized CRLF sequence in these fields terminates the intended command and begins a new one on the same authenticated channel.
The attacker requires no credentials when bearer-token authentication is disabled, which is a common default posture. Injected commands execute under the identity of the upstream mailbox session, granting the attacker the same privileges as the configured mailbox user.
Root Cause
The root cause is missing input neutralization for CRLF byte sequences before parameter values are concatenated into IMAP protocol frames. The service treated folder, UID, and search inputs as opaque strings rather than protocol-sensitive data requiring validation or encoding.
Attack Vector
An attacker sends an HTTP request to the docker-mailbox API with a crafted folder, UID, or search value containing embedded \r\n bytes followed by an IMAP command such as DELETE, FETCH, STORE, or LOGOUT. The bridge writes the concatenated payload to the upstream IMAP socket. The IMAP server parses the injected command as a separate instruction and executes it within the authenticated session.
See the upstream fix commit on GitLab for the exact code paths remediated.
Detection Methods for CVE-2026-82973
Indicators of Compromise
- HTTP request logs containing URL-encoded %0d%0a or raw CRLF bytes in folder, uid, or search parameters targeting the docker-mailbox API.
- Unexpected IMAP tagged responses for commands the bridge did not originate, visible in upstream mail server logs.
- Mailbox state changes such as deleted messages, flag modifications, or new folder operations correlated with anomalous API calls.
Detection Strategies
- Inspect reverse proxy and application logs for control characters in query parameters or JSON body fields destined for /api/mailbox endpoints.
- Correlate docker-mailbox request identifiers with upstream IMAP command volume to detect a single request producing multiple protocol commands.
- Alert on docker-mailbox deployments running versions earlier than 0.4.13 where bearer-token authentication is not enforced.
Monitoring Recommendations
- Enable verbose IMAP command logging on the upstream mail server and forward events to a centralized data lake for correlation.
- Baseline normal command sequences per session and alert on deviations such as unexpected DELETE, EXPUNGE, or LOGOUT operations.
- Monitor container image registries for pulls of psyb0t/docker-mailbox tags older than 0.4.13.
How to Mitigate CVE-2026-82973
Immediate Actions Required
- Upgrade psyb0t/docker-mailbox to version 0.4.13 or later on all deployments.
- Enable bearer-token authentication on every instance, including internal and development environments.
- Restrict network exposure of the docker-mailbox HTTP API to trusted networks or authenticated reverse proxies.
Patch Information
The upstream project remediated the vulnerability in commit 90e6b492d42e011d0ba2c825795b33d054ee6636, released in version 0.4.13. Refer to the GitLab commit for the specific input validation changes applied to folder, UID, and search handling.
Workarounds
- Deploy an upstream web application firewall rule that rejects requests containing \r, \n, %0d, or %0a in parameters passed to the mailbox API.
- Configure bearer-token authentication and rotate tokens immediately after enabling the control.
- Terminate the service behind an authenticated reverse proxy that strips control characters before proxying to docker-mailbox.
# Example WAF-style filter using nginx to reject CRLF in query parameters
location /api/mailbox/ {
if ($args ~* "(%0d|%0a|\r|\n)") {
return 400;
}
proxy_pass http://docker-mailbox:8080;
proxy_set_header Authorization "Bearer $mailbox_token";
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

