CVE-2025-59689
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The malicious input is delivered via a compressed email attachment, which is not an HTTP request but part of email traffic. Such attachments look like normal email content, so a web application firewall cannot reliably distinguish malicious from benign attachments.
Also consider: input validation · RASP
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-59689 being exploited?
Yes. CVE-2025-59689 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-59689?
CVE-2025-59689 is rated Medium with a CVSS score of 6.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-59689?
Yes. A fix has been recorded for CVE-2025-59689. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-59689 affect?
CVE-2025-59689 affects libraesva:email_security_gateway. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 4.5 and < 5.0.31
- affected>= 5.1 and < 5.1.20
- affected>= 5.2 and < 5.2.31
- affected>= 5.3 and < 5.4.8
- affected>= 5.5 and < 5.5.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 27 Sept 2025 (SSVC 2.0.3).
timeline
- 19 Sept 2025Published
- 27 Sept 2025CISA SSVC assessment: exploitation active · 7 days later
- 29 Sept 2025Added to CISA KEV (exploited in the wild) · 2 days later
- 20 Oct 2025CISA remediation due date (US federal agencies) · 21 days later
- 26 Feb 2026CVE record last updated · 130 days (about 4 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linklibraesva.com /security-blog/
- Linkdocs.libraesva.com /knowledgebase/security-advisory-command-injection-vulnerability-cve-2025-59689/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-59689
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.