CASCACascade Atlas

Evidence dossier

CVE-2026-39808

CVE-2026-39808

82.8–97.8Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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>

State
PUBLISHED
Published
Apr 14, 2026
Updated
Jul 17, 2026
Evidence coverage
85%
CISA KEVCatalog member

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

FIRST EPSS84.16%

2026-07-18 · v2026.06.15 · percentile 99.7%

Source stateNo scored conflict

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

fortinetoriginal assertion
container

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>

CISA KEVoriginal assertion
observed_exploitation

Fortinet FortiSandbox OS Command Injection Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.841580000000; percentile 0.996660000000

Applicability

Cited product scope

Trace impact →
FortinetFortiSandbox
[{"status": "affected", "version": "4.4.0", "versionType": "semver", "lessThanOrEqual": "4.4.8"}]unknown
FortinetFortiSandbox PaaS
[{"status": "affected", "version": "23.4.4374"}, {"status": "affected", "version": "23.4.4350"}, {"status": "affected", "version": "23.3.4329"}, {"status": "affected", "version": "23.1.4245"}, {"status": "affected", "version": "22.2.4151"}, {"status": "affected", "version": "22.2.4134"}, {"status": "affected", "version": "22.1.4113"}, {"status": "affected", "version": "21.4.4072"}, {"status": "affected", "version": "21.3.4055"}]unknown
Unknown vendorUnknown product
cpe:2.3:a:fortinet:fortisandbox:*:*:*:*:*:*:*:*; start including 4.4.0; end including 4.4.9supported

Assessments

CVSS by origin

9.8
psirt@fortinet.comCVSS 3.1 · role SecondaryCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.1
fortinetCVSS 3.1 · role unknownCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.