Security Resilience

CVE-2026-114424

RCE

Published
04 November 2026
Modified
09 November 2026
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0026 18th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-114424 is a critical-severity Eval Injection (CWE-95) vulnerability in Seppmail (inferred from references). Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

data and its search condition matches. The validated worker context was root.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1056.003 Web Portal Capture Collection
Adversaries may install code on externally facing portals, such as a VPN login page, to capture and transmit credentials of users who attempt to log into the service.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34399Shared CWE-95
CVE-2026-45293Shared CWE-95
CVE-2023-26323Shared CWE-95
CVE-2026-33618Shared CWE-95
CVE-2026-57149Shared CWE-95
CVE-2026-111687Shared CWE-95
CVE-2026-78497Shared CWE-95
CVE-2026-78847Shared CWE-95
CVE-2025-27603Shared CWE-95
CVE-2026-45579Shared CWE-95

Affected Assets

Seppmail
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.

Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.

Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development can detect eval injection vulnerabilities before deployment.

prevents

Training teaches developers the dangers of eval() with untrusted input and safer alternatives (e.g., ast.literal_eval), so a minority of instances are avoided, but the practice is fallible and the weakness is introduced at code-writing time where many other factors compete, matching the A.8.28 -> CWE-79 / CWE-502 partial rung.

prevents

Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.

finds

A.8.8's reach is published advisories and component inventory; eval injection does surface as CVEs (so not `none`), but the bulk of CWE-95 instances live in first-party code that nobody published an advisory about, which A.8.8's neighbour A.8.29 reaches and A.8.8 does not.

References