CVE-2026-42393: Infoleak

Published Aug 28, 2026
·
Updated

The comparison used for the doveadm password and API key is not fully timing safe and can reveal the length of the configured secret. An attacker with access to the same network as the doveadm service, able to make repeated requests and measure response timing accurately, can learn the length of the secret, which reduces the effort needed to guess it. The secret value itself is not disclosed. Restrict network access to the doveadm service to trusted clients. Update to non-vulnerable version. No publicly available exploits are known.

Affected Software

5 affected componentsFixes available
Dovecot doveadm
debian/dovecot<1:2.3.19.1+dfsg1-2.1+deb12u7
1:2.3.19.1+dfsg1-2.1+deb12u7
debian/dovecot<1:2.4.1+dfsg1-6+deb13u7
1:2.4.1+dfsg1-6+deb13u7
debian/dovecot<1:2.4.5+dfsg1-1
1:2.4.5+dfsg1-1
debian/dovecot<=1:2.3.19.1+dfsg1-2.1+deb12u6, <=1:2.4.1+dfsg1-6+deb13u6
1:2.3.19.1+dfsg1-2.1+deb12u71:2.4.1+dfsg1-6+deb13u71:2.4.5+dfsg1-4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/dovecot to a version that resolves this vulnerability.

    Fixed in 1:2.3.19.1+dfsg1-2.1+deb12u7
  2. Upgrade

    Upgrade debian/dovecot to a version that resolves this vulnerability.

    Fixed in 1:2.4.1+dfsg1-6+deb13u7
  3. Upgrade

    Upgrade debian/dovecot to a version that resolves this vulnerability.

    Fixed in 1:2.4.5+dfsg1-1
  4. Upgrade

    Upgrade debian/dovecot to a version that resolves this vulnerability.

    Fixed in 1:2.3.19.1+dfsg1-2.1+deb12u7Fixed in 1:2.4.1+dfsg1-6+deb13u7Fixed in 1:2.4.5+dfsg1-4
  5. Compensating control

    Restrict network access to the doveadm service to trusted clients.

  6. Operational

    Update to non-vulnerable version.

Event History

Aug 28, 2026
CVE Published
via MITRE·10:12 AM
Data Sourced
via MITRE·10:12 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:16 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·12:16 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Deployments where the doveadm service is reachable by untrusted systems on the same network are exposed. An attacker must be able to send repeated requests and measure response timing accurately.

2

What can an attacker learn from the timing behavior?

The timing difference can reveal the length of the configured doveadm password or API key. It does not disclose the secret value itself, but knowing its length reduces the effort required to guess it.

3

Are credentials or user interaction required to exploit this?

No privileges or user interaction are required, but the attacker needs network access to the doveadm service and the ability to perform repeated, accurate timing measurements.

4

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

Restrict network access to the doveadm service so that only trusted clients can reach it. This limits the ability of an attacker to make the repeated requests needed for timing analysis.

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