CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2025-59032 remediation guide

Open-Xchange GmbH OX Dovecot Pro, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

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.

Open CVE record
ProductOpen-Xchange GmbH OX Dovecot Pro, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support
Affected versions<= 3.1.0, <= 2.4.0, < 2.4.3, < 3.1.3
Fixed versions2.4.3, 3.1.3
Priority basisReview · CVSS 7.5 · EPSS 0.70%
01

Identify the affected asset

Confirm whether Open-Xchange GmbH OX Dovecot Pro, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: <= 3.1.0, <= 2.4.0, < 2.4.3, < 3.1.3. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 2.4.3, 3.1.3. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.