Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Stack-based Buffer Overflow in FortiManager fgtupdates Service

IdentifiersCVE-2025-54820CWE-121· Stack-based Buffer Overflow

CVE-2025-54820 is a high-severity stack-based buffer overflow in the Fortinet FortiManager fgtupdates service. According to the provided content, affected versions are FortiManager 7.4.0 through 7.4.2, 7.2.0 through 7.2.10, and all 6.4 versions; FortiManager 7.6 and FortiManager Cloud are not affected. A remote unauthenticated attacker may trigger the flaw by sending specially crafted requests to the fgtupdates service when that service is enabled. Successful exploitation may allow execution of unauthorized commands, and the content further indicates potential remote code execution risk. Exploitability depends on the attacker’s ability to bypass existing stack protection mechanisms.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow a remote unauthenticated attacker to execute unauthorized commands against the affected FortiManager system. Based on the provided content, this creates potential for remote code execution on a network management platform, which could in turn enable compromise of the appliance, abuse of its privileged management position, and follow-on activity such as lateral movement or persistent access in managed environments.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the fgtupdates service as a temporary workaround. The content specifically recommends removing fgtupdates from the service access list on relevant interfaces to reduce exposure. Administrators should also audit active FortiManager services and monitor for anomalous access to the fgtupdates endpoint.

Remediation

Patch, then assume compromise.

Upgrade to a fixed FortiManager release. The provided content states that FortiManager 7.4.x should be upgraded to 7.4.3 or later, FortiManager 7.2.x should be upgraded to 7.2.11 or later, and all FortiManager 6.4 deployments should be migrated to a fixed supported release. Patching is identified as the primary remediation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortimanageroperating_system
FortinetMultiple Fortinet Productsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.