Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82973 – Unauthenticated IMAP Command Injection (RCE-adjacent) – psyb0t docker-mailbox 0.1.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82973 is a critical CRLF/IMAP command injection vulnerability (CWE-93) in psyb0t’s docker-mailbox project, affecting versions 0.1.0 through 0.4.12. When bearer-token authentication is not configured, a remote unauthenticated attacker can inject arbitrary IMAP commands by supplying CR/LF sequences in HTTP-supplied folder, UID, or search parameters, allowing them to splice attacker-controlled IMAP commands onto the backend’s authenticated mailbox connection. The issue carries a CVSS v3.1 base score of 9.4 (Critical).

Technical details

  • Root cause: docker-mailbox passes HTTP request parameters (folder names, UIDs, and search terms) directly into Python’s imaplib without sanitizing carriage-return/line-feed (CRLF) or NUL characters.
  • Trigger conditions: The vulnerability is exploitable whenever bearer-token authentication is not configured on the service, removing the only barrier to reaching the vulnerable IMAP proxy endpoints.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N). An attacker crafts an HTTP request where a folder, UID, or search field contains a CRLF sequence, terminating the intended IMAP command and appending a second, attacker-chosen IMAP command that is then executed on the authenticated backend mailbox connection.
  • Impact: Low confidentiality impact combined with high integrity and high availability impact (C:L/I:H/A:H) — an attacker can manipulate or disrupt mailbox state and operations by injecting arbitrary IMAP commands into the session.

Affected software

  • psyb0t docker-mailbox versions 0.1.0 through 0.4.12 (inclusive), when bearer-token authentication is not configured.

Severity

  • CVSS v3.1 Base Score: 9.4 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to docker-mailbox version 0.4.13 or later, which adds input validation (_reject_control_chars() and _validate_uid()) that rejects CR, LF, and NUL characters in folder, search, and UID parameters, restricts UIDs to digits and valid sequence-set punctuation, and escapes embedded quotes/backslashes in folder names before they are passed to imaplib.
  • If immediate patching is not possible:
    • Ensure bearer-token authentication is enabled and enforced on all docker-mailbox deployments, as the vulnerability is only exploitable when this authentication is not configured.
    • Restrict network exposure of the docker-mailbox service to trusted networks only; do not expose it directly to the internet.
    • Monitor IMAP backend logs for unexpected or malformed commands that may indicate injection attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge