Forged LFT metadata permits arbitrary file read and deletion
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 15.1.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 15.1.1.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
CVE-2026-114425 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.2 (critical) and affects SEPPmail Secure Email Gateway (SEG); fixed in 15.1.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.33% · 26th 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? →
- 26/100 · provisional
- Fix
- Fixed in 15.1.1
- 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
SEPPmail Secure Email Gateway versions before 15.1.1 are affected by a flaw in how the Large File Transfer feature handles file paths in attachment metadata. Remotely, without logging in, an attacker can send a crafted message that makes the mail-processing worker read, move, or delete any regular file it can access, and because those workers run as root, this can reach sensitive system files; this applies only when LFT is enabled and the message reaches an affected secure-mail processing path.
Read the original description
SEPPmail Secure Email Gateway before 15.1.1 trusts a file path supplied in externally provided Large File Transfer attachment metadata. An unauthenticated remote sender can cause the mail-processing worker to disclose, move, or delete an accessible regular file when LFT is enabled and the message reaches an affected secure-mail processing path. The validated workers ran as root.
What to do
Upgrade to a fixed version: 15.1.1.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
- Posted on X by cve.now
Affected versions
- SEPPmail AG SEPPmail Secure Email Gateway (SEG)
fixed in 15.1.1
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-114425
Is CVE-2026-114425 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
Which versions are affected by CVE-2026-114425?
SEPPmail Secure Email Gateway (SEG): before 15.1.1.Source: cve.now feed data
How do I fix CVE-2026-114425?
Upgrade to a fixed version: 15.1.1.Source: cve.now feed data