Skip to content
major vulnerability· requires attention

Affects a widely deployed Fortinet security product; privilege escalation could disrupt security operations enterprise-wide.

Infrastructure

CVE-2026-39813

9.8
Critical
EPSS 22%Patch availableApr 15, 2026

Path traversal enables privilege escalation in FortiSandbox 4.4.0-4.4.8 and 5.0.0-5.0.5.

common questions

Is CVE-2026-39813 being exploited?

Not confirmed. CVE-2026-39813 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 22% probability of exploitation in the next 30 days.

How severe is CVE-2026-39813?

CVE-2026-39813 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-39813?

Yes. A fix has been recorded for CVE-2026-39813. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-39813 affect?

CVE-2026-39813 affects Fortinet FortiSandbox 4.4.0-4.4.8, Fortinet FortiSandbox 5.0.0-5.0.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-39813?

Patch when available; restrict admin access; monitor FortiSandbox

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Fortinet FortiSandbox 4.4.0-4.4.8Fortinet FortiSandbox 5.0.0-5.0.5
impact

Attacker could escalate to admin on FortiSandbox, gaining full control of the appliance.

action required

Patch when possible

affected versions
Fortinet FortiSandbox
  • affected>= 5.0.0 and <= 5.0.5
  • affected>= 4.4.0 and <= 4.4.8
Fortinet FortiSandbox Cloud
  • affected24.1
  • affected23.4
  • affected>= 5.0.4 and <= 5.0.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free