Persistent code execution via unsigned filesystem images
Published Nov 20, 2025 · Updated Feb 26, 2026
Code integrity failure in SonicWall Email Security 10.0.33.8195 and earlier allows attackers to gain persistent code execution. The appliance loads root filesystem images without verifying their signatures, so modified VMDK-backed files become trusted system files. Exploitation requires access to the VMDK or its datastore and permits persistent modification of the appliance filesystem.
Summary
What happened
Code integrity failure in SonicWall Email Security 10.0.33.8195 and earlier allows attackers to gain persistent code execution. The appliance loads root filesystem images without verifying their signatures, so modified VMDK-backed files become trusted system files. Exploitation requires access to the VMDK or its datastore and permits persistent modification of the appliance filesystem.
The record
- CVE
- CVE-2025-40604
- Published
- Nov 20, 2025
- Updated
- Feb 26, 2026
- Vendor
- SonicWall
- Product
- Email Security
- Classifications
- CWE-494, T1601.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.33.8195 and earlier versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo