# CVE-2026-25836: Command injection in FortiSandbox Cloud

> Privileged attackers with CLI access can execute unauthorized code via crafted HTTP requests in FortiSandbox Cloud and PaaS.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-4j52-3x46-3m7g

## What is CVE-2026-25836?

CVE-2026-25836 is a medium-severity command injection vulnerability in Fortinet FortiSandbox Cloud, published on 10 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox Cloud 5.0.4, FortiSandbox PaaS 5.0.4 may allow  a privileged attacker with super-admin profile and CLI access to execute unauthorized code or commands via crafted HTTP requests.

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

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

It affects 1 product.


Products: Fortinet Fortisandbox Cloud.

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

No fix has been published for CVE-2026-25836 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25836 being exploited?

There is no known exploitation of CVE-2026-25836 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25836 is a medium-severity command injection vulnerability in Fortinet FortiSandbox Cloud, published on 10 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25836 in the wild and no public exploit code.

Affected product: Fortinet FortiSandbox Cloud. 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-25836/ (Markdown: https://insights.sbomify.com/CVE-2026-25836/index.md)
```

## Sources

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

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