Cyber Resilience

CVE-2025-40605

Path Traversal in Sonicwall Email Security Appliance 5000 Firmware ≤ 10.0.33.8195

Published
20 November 2025
Modified
12 December 2025
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0033 25th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-40605 is a medium-severity Relative Path Traversal (CWE-23) vulnerability in Sonicwall Email Security Appliance 5000 Firmware. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 25th 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 SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A Path Traversal vulnerability has been identified in the Email Security appliance allows an attacker to manipulate file system paths by injecting crafted directory-traversal sequences (such as ../) and may access files and directories outside the intended restricted path.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-40604Same product: Sonicwall Email Security Appliance 5000
CVE-2021-20023Same product: Sonicwall Email Security Appliance 5000
CVE-2026-0205Same vendor: Sonicwall
CVE-2024-20310Shared CWE-23
CVE-2025-11898Shared CWE-23
CVE-2026-57988Shared CWE-23
CVE-2025-57403Shared CWE-23
CVE-2026-52813Shared CWE-23
CVE-2025-25130Shared CWE-23
CVE-2026-30345Shared CWE-23

Affected Assets

sonicwall
email security appliance 5000 firmware
≤ 10.0.33.8195
sonicwall
email security appliance 5050 firmware
≤ 10.0.33.8195
sonicwall
email security appliance 7000 firmware
≤ 10.0.33.8195
sonicwall
email security appliance 7050 firmware
≤ 10.0.33.8195
sonicwall
email security appliance 9000 firmware
≤ 10.0.33.8195

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) AI

Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.

Access enforcement directly blocks unauthorized file reads/writes that result from unresolved .. sequences.

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

Least privilege reduces the set of reachable files even when a traversal succeeds.

Secure-engineering principles require safe pathname construction and input neutralization before any file operation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

prevents

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References