CVE-2026-40871 Mailcow SQLi, Vercel Breach & TPM 2.0 Hardware Attestation

This report details the discovery and disclosure of CVE-2026-40871, a high-severity second-order SQL injection vulnerability affecting mailcow-dockerized. The vulnerability specifically resides in the `quarantine_category` field during mailbox creation via the Mailcow UI. Attackers, if they can create mailboxes or compromise an account with mailbox creation privileges, could inject malicious SQL payloads. These payloads would then be executed when subsequent operations access the tainted data, leading to unauthorized data access, modification, or even remote code execution depending on the database configuration and permissions. The criticality stems from the potential for persistent compromise within the mail server environment. A second-order SQL injection often bypasses immediate input validation, as the malicious data is stored and then processed later by a different application component or context. This makes it a tricky vulnerability to detect and mitigate without thorough review of data flow and sanitization practices at all stages of data lifecycle. Organizations running mailcow-dockerized should prioritize patching to the latest version that addresses this CVE to prevent exploitation.

Vercel has officially disclosed a security incident where unauthorized access to its internal systems was detected. The incident investigation has confirmed that customer logs, some internal systems, and private repositories (excluding code) were accessed by the attackers. Critically, the breach also impacted authentication tokens, specifically Github/GitLab/BitBucket tokens and Vercel secrets/tokens. This type of incident underscores the significant risks associated with supply chain compromises, where a breach in a third-party platform can directly expose sensitive assets of its users. As a direct consequence, Vercel is advising all users to take immediate defensive actions. This includes rotating all API keys, OAuth tokens, and other credentials connected to Vercel, especially those used for integration with version control systems like GitHub, GitLab, and BitBucket. Additionally, any sensitive external secrets stored within Vercel environment variables should be considered compromised and rotated. Proactive rotation of these credentials is a critical step in mitigating potential further unauthorized access to linked services and preventing lateral movement by attackers leveraging compromised tokens.

This discussion highlights the often underappreciated value of Trusted Platform Module (TPM) 2.0 in enhancing the security posture of bare-metal server fleets. TPMs are cryptographic co-processors that provide hardware-level security functions, crucial for establishing a root of trust. Specifically, TPM 2.0 enables robust hardware attestation, a process where the system's boot integrity and configuration are cryptographically verified by the TPM itself, reporting any deviations before the system fully boots or connects to a network. This is a foundational element for implementing zero-trust architectures in environments where physical server security is paramount. Hardware attestation ensures that servers are running only authorized firmware and software configurations, guarding against boot-level malware, rootkits, and unauthorized modifications. By leveraging TPM 2.0, organizations can establish a verifiable chain of trust from the hardware up, preventing compromised machines from joining sensitive networks or accessing critical resources. This technique is particularly vital for organizations managing large bare-metal infrastructures, providing a powerful mechanism to detect tampering and enforce policy compliance at the lowest levels of the system stack, thereby strengthening the overall supply chain security of their infrastructure.