CVE-2025-59689: Libraesva Email Security Gateway Command Injection
Libraesva Email Security Gateway · listed in the CISA catalog of actively exploited vulnerabilities since 2025-09-29.
- CVSS v3.1 (CVE record)
- 6.1
- medium
- EPSS (exploit probability, 30 days)
- 2.0%
- higher than 80.8% of all CVEs
- Added to CISA KEV
- 2025-09-29
- US federal due date 2025-10-20
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-59689 explained
CVE-2025-59689 is a command injection vulnerability (CWE-77) in Libraesva Email Security Gateway (ESG) 4.5 through 5.5.x before 5.5.7, triggered via a compressed e-mail attachment. It matters because CISA lists it as known to be exploited, and the gateway processes inbound mail from untrusted senders.
Impact
An unauthenticated attacker can reach the flaw over the network by delivering an e-mail with a crafted compressed attachment. Some user interaction is required, and the scope is changed, meaning effects can extend beyond the vulnerable component. CISA rates the technical impact as total, meaning total control of the affected component. CISA rates it as not automatable. Attackers are known to use this vulnerability.
Who is affected
Libraesva Email Security Gateway versions ≥ 4.5, < 5.0.31, ≥ 5.1, < 5.1.20, ≥ 5.2, < 5.2.31, ≥ 5.3, < 5.4.8 and ≥ 5.5, < 5.5.7 are affected. Fixed versions are 5.0.31, 5.1.20, 5.2.31, 5.4.8 and 5.5.7. Per the record, installations from 4.5 up to the 5.0 branch are covered by the range ending before 5.0.31, and 5.3 installations fall in the range fixed by 5.4.8.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Libraesva Email Security GatewayAffectedFixed in
- ≥ 4.5, < 5.0.31
- ≥ 5.1, < 5.1.20
- ≥ 5.2, < 5.2.31
- ≥ 5.3, < 5.4.8
- ≥ 5.5, < 5.5.7
- 5.0.31
- 5.1.20
- 5.2.31
- 5.4.8
- 5.5.7
| Product | Affected | Fixed in |
|---|---|---|
| Libraesva Email Security Gateway |
|
|
How to fix it
- Update to a fixed version: 5.0.31, 5.1.20, 5.2.31, 5.4.8, 5.5.7.
- Vendor advisory: libraesva.com/security-blog
- CISA's deadline for US federal agencies: 2025-10-20 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify all Libraesva ESG appliances and their installed versions.
- Upgrade to the fixed release for your branch:
5.0.31,5.1.20,5.2.31,5.4.8or5.5.7. - Upgrade
4.5installations to at least5.0.31and5.3installations to at least5.4.8. - Apply any mitigations in the Libraesva advisory, per CISA's required action.
- Check gateways for signs of compromise, since attackers are known to exploit this vulnerability.
- Keep management interfaces of the gateway off the internet.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
Questions about CVE-2025-59689
- Is CVE-2025-59689 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-09-29, with a US federal due date of 2025-10-20. Whether it is used in ransomware campaigns is unknown.
- Which version should I install?
- Install the fixed release for your branch:
5.0.31,5.1.20,5.2.31,5.4.8or5.5.7. For4.5installations the record's affected range ends before5.0.31, and for5.3it ends before5.4.8. - Why does CISA treat it as serious when the CVSS severity is medium?
- CISA rates the technical impact as total, meaning total control of the affected component, and attackers are known to exploit it. The flaw is reachable over the network without authentication via an e-mail attachment.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.