Security Resilience

CVE-2026-114425

Path Traversal

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.0033 26th percentile
Risk Priority 45 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-114425 is a critical-severity External Control of File Name or Path (CWE-73) vulnerability in Seppmail (inferred from references). Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Office Test (T1137.002); ranked at the 26th 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 AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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 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…

more

enabled and the message reaches an affected secure-mail processing path. The validated workers ran as root.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1137.002 Office Test Persistence
Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system.
T1218.008 Odbcconf Stealth
Adversaries may abuse odbcconf.
T1574.006 Dynamic Linker Hijacking Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables the dynamic linker uses to load shared libraries.
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
T1129 Shared Modules Execution
Adversaries may execute malicious payloads via loading shared modules.
T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-39303Shared CWE-73
CVE-2026-21249Shared CWE-73
CVE-2026-61873Shared CWE-73
CVE-2024-9275Shared CWE-73
CVE-2024-43615Shared CWE-73
CVE-2026-76210Shared CWE-73
CVE-2023-36634Shared CWE-73
CVE-2026-30289Shared CWE-73
CVE-2024-0100Shared CWE-73
CVE-2025-6463Shared CWE-73

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)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Enforces authorization checks on the actual resource accessed, blocking unauthorized files even when a malicious path is supplied.

Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.

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 full match
blocks

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

PR.AA-05 mostly match
blocks

Least-privilege file authorization directly limits damage from externally controlled paths.

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 can detect path-traversal issues but does not itself implement preventive controls.

prevents

Training developers about input validation and path handling reduces instances of CWE-73 but is fallible human practice; the weakness is a code-level implementation defect that training alone cannot fully prevent, leaving a nameable remainder of cases where developers still write unvalidated path operations.

prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses like CWE-73 in delivered code the way those practices do, at partial -- the same reading the owner applied to A.8.30 vs CWE-134.

finds

A.8.8's reach is DISCLOSURE-based: it finds CWE-73 where the weakness surfaces as a published advisory in a third-party component (CVE-2022-45918, CVE-2008-5748, CVE-2008-5764 are examples), but the bulk of CWE-73 instances live in first-party code where static analysis and code review — A.8.29's territory — are the High-rated detection methods, leaving the disclosed share a minority.

References