dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 20 Oct 2025.
Email Security GatewayApplication · Libraesva

CVE-2025-59689

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-19
Fix available
A fix is available. Upgrade to 5.0.31 / 5.1.20 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Libraesva Email Security Gateway (ESG) versions 4.5 through 5.5.x before the patched releases contain a command injection vulnerability in the email attachment processing functionality. Attackers can execute arbitrary OS commands by sending specially crafted compressed email attachments to the target ESG appliance.

MitigationUpgrade Libraesva ESG to version 5.5.7 (or the appropriate patched version for the installed branch: 5.0.31, 5.1.20, 5.2.31, or 5.4.8) to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Email Security GatewayApplication
Affected:>= 4.5, < 5.0.31>= 5.1.0, < 5.1.20>= 5.2.0, < 5.2.31>= 5.3.0, < 5.3.16>= 5.4.0, < 5.4.8>= 5.5.0, < 5.5.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Libraesva ESG version
    Access the ESG web interface and navigate to the 'About' or 'System Information' section, or run 'esg-version' or 'cat /etc/*release*' via SSH if available. Note the full version number (e.g., 5.5.3).
    Affected if The version falls within any of these ranges: 4.5 to <5.0.31, 5.1.0 to <5.1.20, 5.2.0 to <5.2.31, 5.3.0 to <5.3.16, 5.4.0 to <5.4.8, or 5.5.0 to <5.5.7.
  2. Confirm compressed attachment processing is active
    Review the ESG configuration via the web UI under 'Content Filters' or 'Attachment Handling' settings. Look for rules that process zip, tar, gz, or other compressed file types in inbound or outbound email flows.
    Affected if Compressed attachment processing rules are enabled and the ESG version is in the affected ranges.
  3. Review email processing logs for suspicious activity
    Access the ESG logs via the web UI (Logs > Mail Logs) or via CLI (typically in /var/log/ or via 'esg logs'). Search for entries involving compressed attachments with unusual patterns or unexpected command execution indicators.
    Affected if Logs contain entries with malformed compressed attachments, unexpected spawn processes, or command strings that resemble injection payloads.

You are affected if your Libraesva ESG version is within the vulnerable ranges AND compressed attachment processing is enabled in your configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.31 / 5.1.20 / 5.2.31 or later
Fixed in 5.0.315.1.205.2.31
Interim mitigation

Upgrade Libraesva ESG to version 5.5.7 (or the appropriate patched version for the installed branch: 5.0.31, 5.1.20, 5.2.31, or 5.4.8) to remediate this vulnerability.

Recommended fix High confidence

Upgrade to the minimum fixed version for your current branch: 5.0.31, 5.1.20, 5.2.31, 5.3.16, 5.4.8, or 5.5.7 (or later)

  1. 1. Identify the currently installed Libraesva ESG version by checking the product dashboard or system information.
  2. 2. Based on the current version, determine the minimum fixed release: For 4.5-5.0.x, upgrade to 5.0.31; for 5.1.x, upgrade to 5.1.20; for 5.2.x, upgrade to 5.2.31; for 5.3.x, upgrade to 5.3.16; for 5.4.x, upgrade to 5.4.8; for 5.5.x, upgrade to 5.5.7.
  3. 3. Obtain the upgrade package from the official Libraesva support portal at docs.libraesva.com or www.libraesva.com.
  4. 4. Review the upgrade documentation and release notes for any prerequisites or migration considerations.
  5. 5. Perform a backup of the current configuration and any critical data.
  6. 6. Apply the upgrade following the vendor's documented upgrade procedure.
  7. 7. After upgrade, verify the version number reflects the patched release.
  8. 8. Test email processing with compressed attachments to confirm functionality remains intact.
Caveat Review release notes for any configuration or behavioral changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Email Security Gateway Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59689 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data