dbcve.org
DovecotApplication

CVE-2025-59032

HIGH · 7.5 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 2.4.3 / 3.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ManageSieve AUTHENTICATE command crashes when using literal as SASL initial response. This can be used to crash ManageSieve service repeatedly, making it unavailable for other users. Control access to ManageSieve port, or disable the service if it's not needed. Alternatively upgrade to a fixed version. No publicly available exploits are known.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ManageSieve AUTHENTICATE command contains a vulnerability where using a literal as the SASL initial response causes the service to crash. An unauthenticated attacker can repeatedly trigger this condition to create a denial-of-service condition, making the ManageSieve service unavailable.

MitigationRestrict network access to the ManageSieve port, disable the ManageSieve service if unnecessary, or upgrade to the vendor-provided fixed version when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DovecotApplication
Affected:< 2.4.3
DovecotApplication
Affected:< 3.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ManageSieve service is enabled
    Check for ManageSieve listener in Dovecot configuration files (typically in /etc/dovecot/conf.d/ or dovecot.conf) and look for 'protocols' or 'service managesieve' entries. On Linux, also check if the service is listening on port 4190 using 'netstat -tlnp | grep 4190' or 'ss -tlnp | grep 4190'.
    Affected if ManageSieve protocol is listed in the protocols setting and the service is listening on its port.
  2. Identify installed Dovecot version
    Run 'dovecot --version' or check the package version using your system package manager (dpkg -l dovecot* or rpm -qi dovecot). For OX Dovecot packages, check 'rpm -qi ox-dovecot' or the equivalent for your package format.
    Affected if The returned version number is lower than 2.4.3 for standard Dovecot or lower than 3.1.3 for Open Xchange Dovecot.
  3. Verify ManageSieve authentication mechanism configuration
    Examine the ManageSieve configuration section in dovecot.conf or conf.d/ directory for 'sieve' or 'managesieve' settings. Look for 'managesieve_implementation_string' and any SASL authentication configuration.
    Affected if ManageSieve is configured and accepting connections; the vulnerability triggers when AUTHENTICATE command receives a literal instead of a string as the SASL initial response.
  4. Confirm service is exposed on network
    Review network binding settings in dovecot.conf for 'listen' directives and firewall rules. Check if port 4190 (default ManageSieve) is open to network traffic using 'iptables -L -n' or 'firewall-cmd --list-all'.
    Affected if The ManageSieve port is bound to a network interface accessible from untrusted networks, increasing exposure to remote attackers.

A user is affected if ManageSieve is enabled and the installed Dovecot version is below 2.4.3 (or below 3.1.3 for Open Xchange variants), and the service is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.3 / 3.1.3 or later
Fixed in 2.4.33.1.3
Interim mitigation

Restrict network access to the ManageSieve port, disable the ManageSieve service if unnecessary, or upgrade to the vendor-provided fixed version when available.

Recommended fix High confidence

Dovecot 2.4.3+ (for 2.x users) or Dovecot 3.1.3+ (for 3.x users)

  1. Identify the currently installed Dovecot version using 'dovecot --version'
  2. Determine if you are running Dovecot 2.x or 3.x branch
  3. For Dovecot 2.x: Upgrade to version 2.4.3 or later
  4. For Dovecot 3.x: Upgrade to version 3.1.3 or later
  5. Use your system's package manager to perform the upgrade (e.g., yum update dovecot or apt install dovecot)
  6. Restart the Dovecot services to apply the update: systemctl restart dovecot
  7. Verify the new version is installed and services are running: dovecot --version && systemctl status dovecot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dovecot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59032 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data