Vulnerability · CVE-2025-46215
An Improper Isolation or Compartmentalization vulnerability [CWE-653] in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions,
Published Nov 18, 2025 · catalog updated Jan 14, 2026 · Fortinet FortiSandbox
Last checked Nov 2, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-46215. EPSS is 0.34%. Act only if a listed version of Fortinet FortiSandbox is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-52436 · High
- CVE-2025-67685 · Low
- CVE-2025-53679 · Medium
- CVE-2025-54353 · Medium
- CVE-2025-53949 · High
- Severity
- Medium5.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.34%
- Remediation
- Vendor / distro source
- Affected products
- vendor Fortinet FortiSandbox 5.0.0 ≤5.0.1
An Improper Isolation or Compartmentalization vulnerability [CWE-653] in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an unauthenticated attacker to evade the sandboxing scan via a crafted file.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Fortinet FortiSandbox 5.0.0 ≤5.0.15.0.0 ≤5.0.1
How to fix CVE-2025-46215
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in 5.0.0 ≤5.0.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-46215. EPSS is 0.34%. Act only if a listed version of Fortinet FortiSandbox is installed.
Which versions are affected?
Compare what you have installed with Fortinet FortiSandbox 5.0.0 ≤5.0.1 5.0.0 ≤5.0.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Nov 18, 2025 · EUVD
Detected
An Improper Isolation or Compartmentalization vulnerability [CWE-653] in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an unauthenticated attacker to evade the sandboxing scan via a crafted file.
Jan 14, 2026 · EUVD
Updated
An Improper Isolation or Compartmentalization vulnerability [CWE-653] in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an unauthenticated attacker to evade the sandboxing scan via a crafted file.
Sources
- CVE.orgVulnerability recordCVE-2025-46215
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-46215
30-day exploitation probability 0.34%
first.org - EUVDVulnerability recordEUVD-2025-198010
An Improper Isolation or Compartmentalization vulnerability [CWE-653] in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an unauthenticated attacker to evade the sandboxing scan vi
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 2, 2026
- CVE.orgOct 27, 2026
- EUVDOct 27, 2026