Threats / Libraesva / CVE-2025-59689
CVE-2025-59689
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Libraesva Email Security Gateway vulnerability
Libraesva Email Security Gateway contains a command injection vulnerability exploitable through compressed email attachments, allowing arbitrary command execution.
Verdict
Today item — known-exploited.
A command injection flaw in Libraesva ESG permits attackers to execute arbitrary commands by crafting malicious compressed email attachments. Active exploitation in the wild confirms practical threat; ransomware deployment risk remains elevated despite current non-ransomware activity.
CISA KEV Yes · 2025-09-295EPSS 0.01913 (verify live)6CVSS 6.13CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-09-29).
Probability (EPSS)
EPSS 0.01913 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) · Affected: Libraesva, Email Security Gateway. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 10 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a compressed email attachment containing shell metacharacters that bypass input validation in the gateway's decompression handler.
Business
Email infrastructure becomes a direct attack vector, bypassing the security appliance intended to protect it.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send the malicious attachment through email to a target organization, triggering automatic processing by the vulnerable ESG instance.
Business
Legitimate email delivery mechanisms are weaponized; the security gateway processes hostile payloads at scale.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve command execution on the ESG appliance itself with the privileges of the email processing service.
Business
The security perimeter is compromised; attackers gain foothold inside the network boundary with access to email traffic and system resources.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05