Skip to main content

FortiSandbox CVE-2026-106172

| EUVDEUVD-2026-98973 MEDIUM
Use of Hard-coded Cryptographic Key (CWE-321)
2026-10-13 fortinet GHSA-99qc-rxm9-wq2h
5.3
CVSS 3.1 · Vendor: fortinet
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach FortiSandbox HTTP interface
  2. Exploit
    Extract hard-coded cryptographic key
  3. Execution
    Forge/sign crafted HTTP request
  4. Impact
    Escalate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

FortiSandbox Cloud 5.0.0 ≤5.0.2
FortiSandbox Cloud 4.4.0 ≤4.4.9
FortiSandbox 5.0.0 ≤5.0.6
FortiSandbox 5.2.0 ≤5.2.1
FortiSandbox Cloud 5.0.4 ≤5.0.6
FortiSandbox 4.4.0 ≤4.4.10

Affected Packages

euvd fortisandbox no fix
euvd fortisandbox_cloud no fix

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

Vendor (fortinet) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
ENISA EUVD HIGH
vuln.today AI 6.5 MEDIUM

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.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (fortinet).

CVSS VectorVendor: fortinet

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

Lifecycle Timeline

2
CVSS changed
Oct 13, 2026 - 18:22 NVD
4.9 (MEDIUM) 5.3 (MEDIUM)
CVE Published
Oct 13, 2026 - 17:37 cve.org
MEDIUM 5.3

DescriptionCVE.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

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
specific Fortinet security appliance, common in enterprises but not ubiquitous
Threat Intel
1
1 sources
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

31
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2026-39808 CRITICAL POC
9.8 Apr 14

OS command injection in Fortinet FortiSandbox 4.4.0-4.4.8 and FortiSandbox PaaS versions 21.3-23.4 enables remote unauth

CVE-2026-25089 CRITICAL POC
9.8 Jun 09

Unauthenticated OS command injection in Fortinet FortiSandbox (on-premise, Cloud, and PaaS variants) allows remote attac

CVE-2026-39813 CRITICAL POC
9.8 Apr 14

Path traversal in Fortinet FortiSandbox 4.4.0-4.4.8 and 5.0.0-5.0.5 enables remote unauthenticated attackers to achieve

CVE-2025-53949 HIGH
8.8 Dec 09

OS command injection in Fortinet FortiSandbox allows an authenticated attacker with low-privilege credentials to execute

CVE-2026-26084 CRITICAL
9.9 Sep 08

Unauthenticated remote access control bypass in Fortinet FortiSandbox 4.2.x through 5.0.x - and its Cloud and PaaS varia

CVE-2026-26083 CRITICAL
9.8 May 12

Remote code execution in Fortinet FortiSandbox 4.4.x through 5.0.x (on-premises, Cloud, and PaaS deployments) allows una

CVE-2025-52436 HIGH
8.8 Feb 10

An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability [CWE-79] vulnerabi

CVE-2024-31491 HIGH
8.8 May 14

A client-side enforcement of server-side security vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.4, FortiSandb

CVE-2024-21756 HIGH
8.8 Apr 09

A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet F

CVE-2024-21755 HIGH
8.8 Apr 09

A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet F

CVE-2021-26096 HIGH
8.8 Aug 04

Multiple instances of heap-based buffer overflow in the command shell of FortiSandbox before 4.0.0 may allow an authenti

CVE-2021-26097 HIGH
8.8 Aug 04

An improper neutralization of special elements used in an OS Command vulnerability in FortiSandbox 3.2.0 through 3.2.2,

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy