Skip to main content
VulnerabilityPublished

CVE-2026-25689: Fortinet FortiDeceptor · Execute Unauthorized Code or Commands

Affects Fortinet FortiDeceptorSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.0 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H/E:F/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
FortinetFortiDeceptorAffected
  • 4.2.0 – 6.2.0
  • >=6.0.0 <=6.0.3
  • >=5.3.0 <=5.3.4
  • >=5.2.0 <=5.2.2
  • >=4.1.0 <=4.1.1
  • >=4.0.0 <=4.0.2
5 affected builds
Fixed in–

CPE configurations (22)

  • cpe:2.3:a:fortinet:fortideceptor:6.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortideceptor:6.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortideceptor:6.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortideceptor:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortideceptor:6.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortideceptor:5.3.4:*:*:*:*:*:*:*

AI-suggested

  1. Apply official patches or updates from Fortinet as soon as they become available to address this vulnerability.
  2. Restrict CLI access strictly to trusted administrators and enforce strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of privilege misuse.
  3. Monitor CLI access logs and network traffic for unusual or unauthorized command executions or HTTP requests targeting the FortiDeceptor interface.
  4. Implement network segmentation to limit access to FortiDeceptor management interfaces, reducing exposure to potential attackers.
  5. Conduct regular security audits and vulnerability assessments on FortiDeceptor deployments to detect configuration weaknesses or unauthorized access.
  6. Educate administrators on the risks of argument injection vulnerabilities and the importance of secure command handling.
  7. Consider deploying additional monitoring tools to detect anomalous file deletions or system changes indicative of exploitation attempts.
  8. Maintain up-to-date backups of FortiDeceptor configurations and critical files to enable recovery in case of destructive attacks.

Description

An improper neutralization of argument delimiters in a command ('argument injection') vulnerability in Fortinet FortiDeceptor 6.2.0, FortiDeceptor 6.0 all versions, FortiDeceptor 5.3 all versions, FortiDeceptor 5.2 all versions, FortiDeceptor 5.1 all versions, FortiDeceptor 5.0 all versions, FortiDeceptor 4.3 all versions, FortiDeceptor 4.2 all versions, FortiDeceptor 4.1 all versions, FortiDeceptor 4.0 all versions may allow a privileged attacker with super-admin profile and CLI access to delete sensitive files via crafted HTTP requests.

References

Community reviews

Loading reviews…