Skip to content
major vulnerability· requires attention

Affects widely deployed FortiManager; high-severity remote RCE risk.

Infrastructure

CVE-2025-54820

8.1
High
EPSS 0.87%Patch availableMar 11, 2026

Remote unauthenticated buffer overflow enables command execution

common questions

Is CVE-2025-54820 being exploited?

Not confirmed. CVE-2025-54820 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 0.87% probability of exploitation in the next 30 days.

How severe is CVE-2025-54820?

CVE-2025-54820 is rated High with a CVSS score of 8.1. 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-2025-54820?

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

What does CVE-2025-54820 affect?

CVE-2025-54820 affects FortiManager 7.4.0-7.4.2, FortiManager 7.2.0-7.2.10, FortiManager 6.4.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-54820?

Patch ASAP; verify updates on affected devices

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

executive summary
technical analysis
affected
FortiManager 7.4.0-7.4.2FortiManager 7.2.0-7.2.10FortiManager 6.4.x
impact

Remote RCE via crafted requests; attacker can run arbitrary commands on FortiManager when service enabled.

action required

Immediate action required

affected versions
Fortinet FortiManager
  • affected>= 7.4.0 and <= 7.4.2
  • affected>= 7.2.0 and <= 7.2.10
  • affected>= 6.4.0 and <= 6.4.15

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