dbcve.org
FortisandboxApplication · Fortinet

CVE-2025-46215

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 4.4.8 / 5.0.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FortiSandbox versions 5.0.0-5.0.1, 4.4.0-4.4.7, 4.2 all, and 4.0 all contain an improper isolation vulnerability (CWE-653) allowing unauthenticated attackers to evade sandbox analysis through specially crafted files. This bypasses the security control designed to safely detonate and analyze potentially malicious content.

MitigationApply vendor-supplied patches for FortiSandbox to remediate the sandbox evasion vulnerability; until patched, implement additional file inspection controls and monitor for indicators of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortisandboxApplication
Affected:>= 4.0.0, < 4.4.8>= 5.0.0, < 5.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FortiSandbox installed version
    Run command: get system status or FortiSandbox CLI: diagnose system version. On web UI, navigate to System > FortiGuard and view the firmware version displayed.
    Affected if Version is 4.0.0 through 4.4.7 inclusive, or 5.0.0 through 5.0.1 inclusive, meaning version is less than 4.4.8 or less than 5.0.2.
  2. Verify sandbox analysis feature is active
    Check if FortiSandbox has submitted files for analysis. In web UI, go to Job View > File Job or use CLI: execute sneep list. Confirm there are recent job entries.
    Affected if The device has been submitting files to the sandbox engine for analysis - the bypass only affects files that would be analyzed by the sandbox.
  3. Review sandbox job status logs for anomalies
    In web UI, go to Log & Report > Security Logs > Sandbox. Look for files marked as 'skipped', 'bypassed', or with unusual status. CLI: execute sneep log and review job completion statuses.
    Affected if Files are showing bypassed/skipped status when they should have been analyzed, or analysis results show unexpected outcomes for known malware test files.
  4. Check for custom evasion detection rules
    Review FortiSandbox configuration at System > Advanced > JSON API. Verify if custom rules exist that may detect or flag evasion attempts. Look for any 'bypass' related configurations.
    Affected if No additional detection rules are configured and the default sandbox behavior is being relied upon exclusively.

A user is affected if their FortiSandbox version falls within 4.0.0-4.4.7 or 5.0.0-5.0.1 and they rely on the sandbox to analyze submitted files, as specially crafted files can evade detection in those versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.8 / 5.0.2 or later
Fixed in 4.4.85.0.2
Interim mitigation

Apply vendor-supplied patches for FortiSandbox to remediate the sandbox evasion vulnerability; until patched, implement additional file inspection controls and monitor for indicators of compromise.

Recommended fix High confidence

FortiSandbox 4.4.8 (or later 4.4.x) or FortiSandbox 5.0.2 (or later 5.0.x)

  1. Upgrade FortiSandbox 4.4.x to version 4.4.8 or later
  2. Upgrade FortiSandbox 5.0.x to version 5.0.2 or later
  3. After upgrade, verify the sandbox evasion protection is working by testing with known malicious file samples
  4. Confirm the FortiGuard security metadata is updated to the latest version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46215 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46215 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data