CVE-2026-42006: An attacker can cause uncontrolled memory usage with excessive bracing over IMAP.
An attacker can cause uncontrolled memory usage with excessive bracing over IMAP. The fix in CVE-2026-27857 was incomplete, only blocking one way of doing this, so there was still another way left open. In particular, the fix was for closing braces, but you could still use open braces to bypass the limit. Using excessive bracing, attacker can cause memory usage up to configured memory limit. Install fixed version, or configure vsz_limit for imap process to low value. No publicly available exploits are known.
Security readout for executives and security teams
Plain-English summary
A remote attacker can send malformed IMAP input containing excessive opening braces, forcing the mail service to consume memory up to its configured limit. This can disrupt email availability without authentication or user interaction. The earlier CVE-2026-27857 fix did not close this alternate path.
Executive priority
Prioritize remediation for internet-facing or business-critical IMAP systems. Although no public exploitation is reported, unauthenticated remote availability impact and an incomplete previous fix justify prompt patching. Confirm exact affected versions through vendor guidance because the supplied version metadata is incomplete.
Technical view
CVE-2026-42006 is a network-reachable resource-exhaustion flaw affecting OX Dovecot Pro. Excessive opening braces bypass the incomplete closing-brace restriction from CVE-2026-27857. CVSS 3.1 is 7.5, reflecting unauthenticated, low-complexity denial of service with high availability impact but no stated confidentiality or integrity impact.
Likely exposure
Systems are most exposed when affected OX Dovecot Pro IMAP services are network-reachable. The supplied affected-version data lists placeholder values and does not establish precise vulnerable releases. Administrators must compare installed builds with the Open-Xchange advisory and applicable Red Hat errata.
Exploitation context
No publicly available exploits are known, and the CVE is not identified as a CISA KEV entry in the supplied bundle. Exploitation nevertheless requires no privileges or user interaction and can occur remotely over IMAP, making exposed services credible denial-of-service targets.
Researcher notes
The weakness maps to CWE-400 and CWE-770. The important distinction from CVE-2026-27857 is that closing braces were constrained while opening braces remained usable to evade the intended limit. The bundle states memory can grow to the configured ceiling; it does not establish code execution, data disclosure, or publicly available exploit tooling.
Mitigation direction
Install the fixed version identified by Open-Xchange or the applicable Red Hat erratum.
Until updated, configure a low, operationally tested vsz_limit for IMAP processes.
Restrict unnecessary public IMAP exposure using existing network access controls.
Monitor IMAP process memory and service restarts for abnormal resource consumption.
Validation and detection
Inventory OX Dovecot Pro and related Red Hat packages serving IMAP.
Compare installed package builds with the vendor advisory and applicable Red Hat errata.
Confirm IMAP processes have an appropriately low, tested vsz_limit.
Review monitoring data for unusual IMAP memory growth, crashes, or repeated restarts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.