CVE-2026-40203: Infoleak

Published Aug 28, 2026
·
Updated

When IMAP compression is enabled, the same compression state is reused across responses in a session, so response sizes depend on both attacker-supplied mail and other mail in the same mailbox. An attacker that can send mail to a user and can also observe the sizes of that user's IMAP traffic can confirm whether the body of a small message matches a guessed text. Recovery of arbitrary unknown content was not demonstrated, but the attack can disclose whether a secret-like message body matches a candidate. Disable IMAP compression. Update to non-vulnerable version. No publicly available exploits are known.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in non-vulnerable version
  2. Configuration

    Disable IMAP compression so that the attacker cannot confirm whether the body of a small message matches guessed text by observing IMAP response sizes.

    IMAP IMAP compression = disabled

Event History

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

Frequently Asked Questions

1

What conditions must an attacker meet to exploit this issue?

The attacker must be able to send email to the target user and observe the sizes of that user's IMAP traffic. IMAP compression must also be enabled for the affected session.

2

Who is realistically exposed?

Users whose mailboxes can receive attacker-supplied messages and whose IMAP traffic sizes can be observed are exposed when IMAP compression is enabled. The disclosed impact is confirmation that a small message body matches attacker-guessed text.

3

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

Disable IMAP compression. This removes the reused compression state that makes response sizes dependent on other mailbox content.

4

Is exploitation known to recover arbitrary mailbox content?

No. Recovery of arbitrary unknown content was not demonstrated; the described attack confirms whether a secret-like message body matches a candidate.

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