CVE-2025-46215VulnerabilityPublished 18 Nov 2025Updated 14 Jan 2026

CVE-2025-46215: Fortinet FortiSandbox · Execute unauthorized code or commands

Affects Fortinet FortiSandboxSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiSandbox	Affected =5.0.0 =4.4.0 =4.2.1 =4.0.0	Fixed in–

AI-suggested

1. Immediate mitigation should focus on upgrading FortiSandbox to the latest patched versions once Fortinet releases security updates addressing CVE-2025-46215. 2. Until patches are available, implement strict file submission policies to limit exposure to untrusted or suspicious files, including enhanced filtering and validation at network ingress points. 3. Employ network segmentation to isolate FortiSandbox systems from general user networks, reducing the attack surface. 4. Monitor FortiSandbox logs and network traffic for anomalies indicative of sandbox evasion attempts or unusual file submissions. 5. Deploy complementary security controls such as endpoint detection and response (EDR) and intrusion detection systems (IDS) to detect malicious activity that may bypass sandboxing. 6. Conduct regular vulnerability scanning and penetration testing focused on FortiSandbox environments to identify potential exploitation attempts. 7. Educate security teams about this vulnerability and update incident response plans to include detection and containment strategies for sandbox evasion techniques. 8. Coordinate with Fortinet support for guidance and timely information on patches and mitigation best practices.

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.

Impact

For European organizations, the primary impact of CVE-2025-46215 is the potential bypass of malware detection and sandboxing defenses, which undermines the integrity of security operations. Attackers exploiting this vulnerability can submit malicious files that are not properly analyzed or contained, increasing the risk of malware infiltration and lateral movement within networks. This can lead to prolonged undetected compromises, data manipulation, or preparation for further attacks. While confidentiality and availability are not directly impacted by this vulnerability, the erosion of trust in sandbox results can degrade overall security posture. Organizations in sectors such as finance, government, healthcare, and critical infrastructure that rely heavily on FortiSandbox for threat detection are particularly vulnerable. The lack of authentication requirement and user interaction lowers the barrier for exploitation, increasing risk. Additionally, the vulnerability could be leveraged as part of multi-stage attacks targeting European entities, especially those with high Fortinet product adoption.

References

fortiguard.fortinet.com/psirt/FG-IR-24-501 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 14:45 UTC

Technical details

References

Community reviews

Related threats