Attack Chain

1. An attacker crafts a malicious API request to the /api/v1/add/mailbox endpoint.
2. The malicious request includes a crafted quarantine_category value containing SQL injection payloads.
3. The mailcow application stores the unsanitized quarantine_category value in the database.
4. The quarantine_notify.py script is executed as part of the quarantine notification job.
5. quarantine_notify.py constructs a SQL query using the stored, malicious quarantine_category value and unsafe string formatting.
6. The injected SQL code is executed against the database, allowing the attacker to perform arbitrary SQL operations.
7. The attacker uses UNION SELECT statements to extract sensitive data, such as admin credentials.
8. The extracted data is included in quarantine notification emails, potentially exposing it to the attacker or other unintended recipients.

Impact

Successful exploitation of this vulnerability allows attackers to inject arbitrary SQL commands into the mailcow: dockerized database. This could lead to the exfiltration of sensitive information, such as admin credentials, API keys, or user data. The exfiltrated data can then be used for further malicious activities, including account takeover, data breaches, or privilege escalation. Although the exact number of potential victims is unknown, any mailcow: dockerized instance running a version prior to 2026-03b is susceptible.

Recommendation

• Upgrade mailcow: dockerized to version 2026-03b or later to patch CVE-2026-40871.
• Implement input validation and sanitization for the quarantine_category field in the /api/v1/add/mailbox endpoint to prevent SQL injection attacks.
• Deploy the Sigma rule Detect Mailcow Unsafe Quarantine Category Update to detect suspicious API requests containing potential SQL injection payloads targeting the /api/v1/add/mailbox endpoint.
• Review and update the quarantine_notify.py script to use parameterized queries instead of unsafe string formatting to prevent SQL injection vulnerabilities.