Code execution through double evaluation in address replacement rules
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-114424 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.26% · 18th 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 before the fixed release can evaluate attacker-controlled replacement text as Perl code in sender or recipient replacement rules, letting an unauthenticated remote sender run operating-system commands with root privileges in the mail-processing worker. The flaw is reached remotely over the network without logging in, and it only applies when an active rule uses message-derived replacement data and its search condition matches.
Read the original description
SEPPmail Secure Email Gateway before 15.1.1 can evaluate attacker-influenced replacement text as Perl code in sender or recipient replacement rules. An unauthenticated remote sender can execute operating-system commands in the mail-processing worker context when an active rule uses message-derived replacement data and its search condition matches. The validated worker context was root.
What to do
Upgrade to a fixed version: 15.1.1.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
- 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-114424
Is CVE-2026-114424 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-114424?
SEPPmail Secure Email Gateway (SEG): before 15.1.1.Source: cve.now feed data
How do I fix CVE-2026-114424?
Upgrade to a fixed version: 15.1.1.Source: cve.now feed data