Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach FortiSandbox HTTP interface
-
ExploitExtract hard-coded cryptographic key
-
ExecutionForge/sign crafted HTTP request
-
ImpactEscalate privilege on appliance
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | The attacker must be able to reach the FortiSandbox (or FortiSandbox Cloud) HTTP/management interface over the network and possess the hard-coded cryptographic key embedded in the firmware, which is used to construct trusted 'specially crafted HTTP requests.' Per CVSS PR:N/UI:N, no valid credentials or user interaction are required once the static key is known. Affected deployments are limited to specific versions: FortiSandbox 5.2.0-5.2.1, 5.0.0-5.0.6, and all 4.4; and FortiSandbox Cloud 5.2.0-5.2.1, 5.0.0-5.0.6, and all 4.4. The primary limiting factor is network exposure of the management interface - appliances whose HTTP interface is not reachable by the attacker are not exploitable from that path. |
| Impact | This is a moderate-severity issue (official CVSS 5.3) that should be patched but does not represent an emergency. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N indicates network-reachable, low-complexity, unauthenticated exploitation requiring no user interaction - favorable conditions for an attacker. However, the declared impact is limited to low confidentiality only (C:L/I:N/A:N), which is in tension with the description's claim of 'escalation of privilege': a genuine privilege escalation would normally carry an integrity or scope impact, so the low-only rating suggests the escalation is narrow or partial - verify the exact privilege gained with Fortinet. No EPSS score, CISA KEV listing, or POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the risk is therefore driven by the vulnerability's inherent reachability rather than any observed in-the-wild activity. The hard-coded cryptographic key (CWE-321) is the core weakness: once the static key is extracted from firmware, exploitation becomes trivial and automatable, which could rapidly change the risk picture if a POC emerges. Net assessment: a credible, patch-worthy flaw in a security appliance, but currently a standard-priority item absent exploitation signals, not a drop-everything critical. |
| Exploit ScenarioDerived | An attacker with network access to the FortiSandbox management/HTTP interface leverages the hard-coded cryptographic key - recoverable from the firmware or shared across all deployments - to forge or sign specially crafted HTTP requests that the appliance trusts. This lets the attacker gain unauthorized access to privileged functionality or data without valid credentials. No public exploit code was identified in the provided data, but the static-key nature means a reliable exploit would be straightforward to develop once the key is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
FortiSandbox and FortiSandbox Cloud ship with a hard-coded cryptographic key that is used to validate or sign trusted HTTP requests, allowing an unauthenticated remote attacker who knows that static key to craft requests the appliance treats as legitimate and thereby escalate privileges. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, official score 5.3), no valid credentials or user interaction are required once the embedded key is known, though exploitation is limited to deployments that expose the HTTP/management interface to the attacker's network. Affected versions are FortiSandbox 5.2.0-5.2.1, 5.0.0-5.0.6 and all 4.4 releases, plus the corresponding FortiSandbox Cloud versions; there is no public exploit identified at time of analysis, but the issue is authoritative-moderate severity and should be remediated rather than treated as an emergency.
RemediationAI
Fortinet's PSIRT advisory FG-IR-26-179 (https://fortiguard.fortinet.com/psirt/FG-IR-26-179) is the authoritative remediation reference; the data available here does not include an exact fixed version, so administrators should consult that advisory for the corrected release line and upgrade the appliance accordingly - vendor-released patch availability for the specific train is not independently confirmed in this dataset, and no exact fix version should be assumed. FortiSandbox Cloud is a hosted service, so tenant-side action is limited to confirming the fix with Fortinet support rather than upgrading locally. Until an upgrade is applied, the most effective compensating control is to stop exposing the HTTP/management interface to untrusted networks: restrict it to a dedicated management VLAN or jump host with explicit firewall/ACL rules, require VPN access for administrators, and disable remote management on interfaces reachable from the internet. Because the hard-coded key cannot be rotated by the customer, network isolation is the only durable mitigation short of patching; the trade-off is that tightening access breaks remote administration, API integrations, and any automation that reaches the management interface from outside the restricted segment, so those consumers must be re-homed or proxied. Additionally, review HTTP access logs for requests bearing unexpected or anomalous authorization/signature headers from non-management source addresses, and monitor for unusual privileged configuration changes, as these are the observable traces of abuse of a trusted static key.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-321 (Use of Hard-coded Cryptographic Key): rather than deriving keys per-installation or storing them in protected, rotatable storage, FortiSandbox firmware embeds a static cryptographic secret. Because the same key exists across installations of the affected versions, any party that extracts it - from firmware images, prior disclosures, or reverse engineering - can generate request signatures or tokens that the appliance validates as coming from a trusted source. The vulnerability is therefore a trust-boundary defect in the HTTP/management communication path of the FortiSandbox virtual appliance and the FortiSandbox Cloud service, rather than a memory-safety or injection flaw. CPE data confirms the two affected product trees (cpe:2.3:a:fortinet:fortisandbox and cpe:2.3:a:fortinet:fortisandbox_cloud), and the Fortinet PSIRT advisory FG-IR-26-179 is the vendor's canonical reference for the affected builds and any fixed releases. Because the key is static and shared, the standard cryptographic property that compromise of one host does not compromise others does not hold - a single leak of the key degrades the authentication guarantee for every unpatched instance.
Know when Fortisandbox gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-reachable crafted HTTP requests (AV:N/AC:L) using a shared hard-coded key bypass authentication (PR:N/UI:N); privilege escalation implies at least low integrity alongside the vendor's low confidentiality impact.
Primary rating from Vendor (fortinet).
CVSS VectorVendor: fortinet
Lifecycle Timeline
2DescriptionCVE.org
A use of hard-coded cryptographic key vulnerability in Fortinet FortiSandbox 5.2.0 through 5.2.1, FortiSandbox 5.0.0 through 5.0.6, FortiSandbox 4.4 all versions, FortiSandbox Cloud 5.2.0 through 5.2.1, FortiSandbox Cloud 5.0.0 through 5.0.6, FortiSandbox Cloud 4.4 all versions may allow attacker to escalation of privilege via specially crafted HTTP requests
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Fortisandbox
View allOS command injection in Fortinet FortiSandbox 4.4.0-4.4.8 and FortiSandbox PaaS versions 21.3-23.4 enables remote unauth
Unauthenticated OS command injection in Fortinet FortiSandbox (on-premise, Cloud, and PaaS variants) allows remote attac
Path traversal in Fortinet FortiSandbox 4.4.0-4.4.8 and 5.0.0-5.0.5 enables remote unauthenticated attackers to achieve
OS command injection in Fortinet FortiSandbox allows an authenticated attacker with low-privilege credentials to execute
Unauthenticated remote access control bypass in Fortinet FortiSandbox 4.2.x through 5.0.x - and its Cloud and PaaS varia
Remote code execution in Fortinet FortiSandbox 4.4.x through 5.0.x (on-premises, Cloud, and PaaS deployments) allows una
An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability [CWE-79] vulnerabi
A client-side enforcement of server-side security vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.4, FortiSandb
A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet F
A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet F
Multiple instances of heap-based buffer overflow in the command shell of FortiSandbox before 4.0.0 may allow an authenti
An improper neutralization of special elements used in an OS Command vulnerability in FortiSandbox 3.2.0 through 3.2.2,
EUVD-2026-98973
GHSA-99qc-rxm9-wq2h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB