CVE
MailEnable Save Directory Traversal Arbitrary File Creation Vulnerability
Affects MailEnable installations; fixed in version 10.60. CVSS rates it high (7.4).
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 10.60
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.60.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 1.48% · 74th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
MailEnable is affected by a directory traversal flaw in its Save method that lets a remote attacker create arbitrary files without logging in. The attacker can combine this with other vulnerabilities to run code as SYSTEM.
Read the original description
MailEnable Save Directory Traversal Arbitrary File Creation Vulnerability. This vulnerability allows remote attackers to create arbitrary files on affected installations of MailEnable. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the implementation of the Save method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of SYSTEM. Was ZDI-CAN-29161.
Who should check
Teams running MailEnable installations, where the advisory names version 10.60 as the fixed release.
Read the source excerpt
“This vulnerability allows remote attackers to create arbitrary files on affected installations of MailEnable.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.4/10CVSS 7.4
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10.60.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-114556 (MailEnable Save Directory Traversal Arbitrary File Creation Vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-114556 (entry last updated 2026-11-12):
Affected:
- MailEnable MailEnable: versions 10.59
Fixed versions: 10.60.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-114556 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114556 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zerodayinitiative.com/advisories/ZDI-26-869/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-114556
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114556"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- MailEnable MailEnable
10.59
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-114556
Is CVE-2026-114556 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A remote attacker can create arbitrary files on affected MailEnable installations through a directory traversal flaw. The attacker could combine this with other vulnerabilities to execute code as SYSTEM.Source: zerodayinitiative.com
Which versions are affected by CVE-2026-114556?
MailEnable: version 10.59.Source: cve.now feed data
Am I affected, and how do I check?
The checked facts do not list affected version ranges, so the exact affected versions are not stated here. To check an installation, compare its MailEnable version with the fixed version, 10.60.Source: zerodayinitiative.com
How do I fix CVE-2026-114556?
Upgrade MailEnable to version 10.60, which is the fixed version named for this vulnerability.Source: zerodayinitiative.com