# CVE-2026-39808: Fortinet FortiSandbox OS Command Injection

> An attacker can execute unauthorized code or commands on Fortinet FortiSandbox due to improper neutralization of special elements in OS commands.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 16 Jul 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-wfjv-vrx5-2cf2

## What is CVE-2026-39808?

CVE-2026-39808 is a critical command injection vulnerability in Fortinet Fortisandbox, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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>

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-39808?

It affects 1 product.


Products: Fortinet Fortisandbox.

## How do I fix CVE-2026-39808?

No fix has been published for CVE-2026-39808 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Jul 2026.

## Is CVE-2026-39808 being exploited?

Yes. Attackers have exploited CVE-2026-39808 in the wild since at least 16 Jul 2026.

Public exploit code:

- FortiSandbox RCE Scanner — CVE-2026-39808 (github_poc): https://github.com/ynsmroztas/FortiSandbox-RCE-Exploit-CVE-2026-39808
- PoC for Unauthenticated RCE in FortiSandbox via CVE-2026-39808 (github_poc): https://github.com/samu-delucas/CVE-2026-39808
- CVE-2026-39808 (github_poc): https://github.com/0xredash/CVE-2026-39808
- An unauthenticated OS command injection vulnerability (github_poc): https://github.com/gotr00t0day/CVE-2026-39808
- CVE-2026-39808 - Fortinet Sandbox - Draft (github_poc): https://github.com/HORKimhab/CVE-2026-39808
- Fortinet FortiSandbox 4.4.0-4.4.8 - OS Command Injection via tracer-behavior Endpoint (github_poc): https://github.com/error-inside/CVE-2026-39808

## Other vulnerabilities in Fortinet Fortisandbox

- [CVE-2026-25089](https://insights.sbomify.com/CVE-2026-25089/): Fortinet FortiSandbox OS Command Injection (critical 9.1, exploited in the wild)
- [CVE-2026-26083](https://insights.sbomify.com/CVE-2026-26083/): Missing authorization in FortiSandbox (critical 9.1)
- [CVE-2026-39813](https://insights.sbomify.com/CVE-2026-39813/): Path traversal in FortiSandbox (critical 9.1)
- [CVE-2020-29011](https://insights.sbomify.com/CVE-2020-29011/): SQL injection in Fortinet FortiSandbox (high 8.8)
- [CVE-2021-26097](https://insights.sbomify.com/CVE-2021-26097/): Command injection in Fortinet FortiSandbox (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39808 and fix it if it is affected.

What it is: CVE-2026-39808 is a critical command injection vulnerability in Fortinet Fortisandbox, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-39808 in the wild since at least 16 Jul 2026.

Affected product: Fortinet Fortisandbox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39808/ (Markdown: https://insights.sbomify.com/CVE-2026-39808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39808
- OSV: https://osv.dev/vulnerability/CVE-2026-39808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39808/
Summaries are generated and may contain mistakes; the official description above is the record.