How severe is CVE-2025-59689?

CVE-2025-59689 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-59689?

Affected package information for CVE-2025-59689 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-59689?

No fixed version has been published for CVE-2025-59689 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2025-59689 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-59689 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-59689?

CVE-2025-59689 has an EPSS (Exploit Prediction Scoring System) score of 6.9%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-59689 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-59689 (Libraesva Email Security Gateway Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-09-29. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-10-20. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-59689?

CVE-2025-59689 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2025-59689?

CVE-2025-59689 affects libraesva email security gateway. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2025-59689 published, and has it been updated?

CVE-2025-59689 was published on September 19, 2025 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2025-59689: Email Security Gateway CWE-77 (Medium 6.1)

EPSS Exploitation Probability

via FIRST.org ↗

6.9%probability of exploitation in next 30 days

Lower Risk92th percentile+0.91%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Libraesva ESG 4.5 through 5.5.x before 5.5.7 allows command injection via a compressed e-mail attachment. For ESG 5.0 a fix has been released in 5.0.31. For ESG 5.1 a fix has been released in 5.1.20. For ESG 5.2 a fix has been released in 5.2.31. For ESG 5.4 a fix has been released in 5.4.8. For ESG 5.5. a fix has been released in 5.5.7.

Affected Products

1 product · 6 configurations

Application

email security gatewaylibraesva

≥ 5.5.0 && < 5.5.7

range

Frequently Asked Questions

Libraesva ESG 4.5 through 5.5.x before 5.5.7 allows command injection via a compressed e-mail attachment. For ESG 5.0 a fix has been released in 5.0.31. For ESG 5.1 a fix has been released in 5.1.20. For ESG 5.2 a fix has been released in 5.2.31. For ESG 5.4 a fix has been released in 5.4.8. For ESG 5.5. a fix has been released in 5.5.7.

O3 Security · Impact-Aware SCA

Is CVE-2025-59689 in your stack?

O3 detects CVE-2025-59689 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works