Skip to content
Fencer Intel
critical 9.8

CVE-2025-64155 in the critical feed json

An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSIEM 7.4.0, Fo…

published 9mo ago modified 4mo ago also EUVD-2026-2076

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
43.9%
EPSS 43.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSIEM 7.4.0, FortiSIEM 7.3.0 through 7.3.4, FortiSIEM 7.1.0 through 7.1.8, FortiSIEM 7.0.0 through 7.0.4, FortiSIEM 6.7.0 through 6.7.10 may allow an attacker to execute unauthorized code or commands via crafted TCP requests.

Patch / fix

  • fortinet fortisiem 7.1.9, 7.2.7, 7.3.5

Is CVE-2025-64155 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
9mo ago

Exploit prediction

43.87% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/horizon3ai/CVE-2025-64155 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/purehate/CVE-2025-64155-hunter referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Fortinet FortiSIEM

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.