CVE-2026-40017: Medium severity IMAP THREAD command vulnerability

Published Aug 28, 2026
·
Updated

An attacker that can send mail to a user can craft a message header whose values are chosen to collide in an internal hash table, which makes the IMAP THREAD command consume CPU disproportionate to the size of the message. This is a separate issue from CVE-2026-40014 and is not addressed by that fix. Whenever a mail client issues a THREAD command on the affected mailbox, this can cause degradation or denial of service for IMAP. Monitor system for abnormal CPU usage, kill the offending process and remove the offending message from the affected mailbox. Update to non-vulnerable version. No publicly available exploits are known.

Affected Software

1 affected component
IMAP THREAD command

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Monitor system CPU usage for abnormal spikes caused by IMAP THREAD commands on the affected mailbox; if detected, kill the offending process.

  2. Operational

    After killing the offending process, remove the offending message from the affected mailbox.

Event History

Aug 28, 2026
CVE Published
via MITRE·10:12 AM
Data Sourced
via MITRE·10:12 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can trigger the issue?

An attacker must be able to send email to a user whose mailbox is processed with the IMAP THREAD command. No authentication to the IMAP service is described as necessary for the attacker.

2

When does the denial of service occur?

The crafted message causes impact when a mail client issues a THREAD command on the affected mailbox. The command can consume disproportionate CPU and degrade or deny IMAP service.

3

What can be done if an update cannot be applied immediately?

Monitor for abnormal CPU usage. If the issue is triggered, kill the offending process and remove the offending message from the affected mailbox.

4

Does the fix for CVE-2026-40014 address this issue?

No. This issue is separate from CVE-2026-40014 and is not addressed by that fix.

5

Are public exploits available?

No publicly available exploits are known.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203