cve.bz

CVE-2026-39808 Fortinet FortiSandbox OS Command Injection Vulnerability

9.8 criticalKEVExploit referenceEPSS 93%

Critical (9.8) in Fortinet FortiSandbox. In CISA KEV since 2026-07-16. EPSS 93% estimated probability of exploitation activity in the next 30 days.

On this page
A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.8 may allow attacker to execute unauthorized code or commands via <insert attack vector here>

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
93% (unchanged from 93% a week ago; 47% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-07-16, due 2026-07-19
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-04-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-39808 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-39808?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-39808?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-39808 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-39808

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-39808](https://cve.bz/cve/badge/CVE-2026-39808.svg)](https://cve.bz/cve/CVE-2026-39808)

HTML:

<a href="https://cve.bz/cve/CVE-2026-39808"><img src="https://cve.bz/cve/badge/CVE-2026-39808.svg" alt="CVE-2026-39808"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Fortinet FortiSandboxfrom 4.4.0 through 4.4.8
Fortinet FortiSandbox PaaS23.4.4374
Fortinet FortiSandbox PaaS23.4.4350
Fortinet FortiSandbox PaaS23.3.4329
Fortinet FortiSandbox PaaS23.1.4245
Fortinet FortiSandbox PaaS22.2.4151
Fortinet FortiSandbox PaaS22.2.4134
Fortinet FortiSandbox PaaS22.1.4113
Fortinet FortiSandbox PaaS21.4.4072
Fortinet FortiSandbox PaaS21.3.4055

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

3 more
  • error-inside/CVE-2026-39808 0 stars, Python, created
    Fortinet FortiSandbox 4.4.0-4.4.8 - OS Command Injection via tracer-behavior Endpoint
  • HORKimhab/CVE-2026-39808 0 stars, created
    CVE-2026-39808 - Fortinet Sandbox - Draft
  • Lechansky/CVE-2026-39808 0 stars, created
    Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (CWE-78)

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON